|RE: [cdt-dev] Make Target View|
I came up with enhanced dialog, could you take a look and share your thoughts about it? The most significant part is a relation of a Build Target to Configuration and Project Builders. How does it fit to overall concept and does it connect well to Managed Build?
We had a similar desire: https://bugs.eclipse.org/bugs/show_bug.cgi?id=224640 . Our Make Target dialog is almost identical to yours -- we have a grouping for tying the Make Target to a particular build configuration. Presumably you put in some additional infrastructure to run the Scanner Discovery builder in the context of the specified configuration?
While the above worked, I didn't submit a patch due to the massive performance problems I encountered. Make targets are most useful for people who do not have a single 'make all' target which builds their tree. They may have multiple targets that build the same files with different -Ds and -Is producing different binaries. It's then natural to tie some target(s) to a given configuration. I did this using the PerFileSICollector -- not wanting to make any assumptions on what was defined / undefined on per file basis. The resulting cproject file grew to a few megabytes in size, with any subsequent operations on the Project model taking 10s of seconds using hundreds of megabytes of memory. I had Eclipse taking >1min to load the .cproject file and start up, and was experiencing OOM exceptions doing simple things like changing a build setting.
The result was I gave up, and did this instead https://bugs.eclipse.org/bugs/show_bug.cgi?id=236872 .
Have you experienced serious issues with scalability doing what you're doing? Are you using the PerProject or PerFile collector? I'd be very interested to know if and how you got this working successfully...
Back to the top