| [cdt-dev] CDT build config references versus Platform project references |
|
Hey gang,
Playing with some real world projects, I was trying to set up build configs for a group of projects. Each project could have up to 8 build configs. There's a executable project and about 5 library projects and I'm trying to set up the dependencies between
the executable and the libraries for configs of the same names. Now when you switch configs, it's actually pretty difficult to ensure that the configs are set the same for all projects. Luckily the CDT builders follows the config dependencies and ensures that
the dependent projects are build properly. However, the Platform project references will also trigger a build of potentially the wrong config, or build a project a second time, which is a waste of time.
So the question I have, do we really need to set the platform project reference when we create a build config dependency in the Paths and Symbols -> References tab?
The downside is Build All which may build things out of order, but then again, the CDT builder will redo the project builds as needed. Or is there a better way to do this?
Have we had this conversation before?
Thanks,
Doug.
|