| AW: [cdt-dev] Adding MakeTargets takes a long time and consumes ahuge amount of heap |
What is your workflow, do you generate exactly the same targets in each folder?
No, I don't generate the same targets in each folder. First of all I don't generate MakeTargets in every folder of the project, only in specific ones.I am searching some kind of makefiles in specific folders. Then I parse them for special keywords and depending on that keyword I create a set of MakeTargets. Another thing is that the build process is used for different target systems, i.e. depending on the selected target a folder with the name of this target is created. As a result of this build process some files are generated inside these newly created target folders where I want to add additional MakeTargets. What I am doing now is that I look into every folder that I find and create the MakeTargets if the needed files exist. I don't know if all this is possible with your proposed way, but it sounds interesting.
Do you think it might be a good idea to have some kind of "generic" targets defined on project (or even workspace) level and have Make Targets view to display them in each folder? This way scalability issue could be avoided. I've done something similar before. To get it working Make Target view has to be modified, (or a new view can be created being with a copy of Make View if done as a plugin). Well, this may be even more work, but I'd like to know in general if this approach would suit your workflow.
I assume your MakeTargets were exactly the same for every folder you added them to, right? Did you add the MakeTargets to every folder or only to specific ones? Do you have some kind of check if you should display a target in a folder or not? The problem that I see with this approach is that I would have to make my decisions which target to display every time I open the view again, right?
Regards,
Thomas