The indexer using platform project references is news to me. So you're saying a properly configured project needs its project references described in two places. Yikes. It sounds
to me that's the first thing that needs to be tackled, and on the surface doesn't sound like it should be very difficult.
I'll add that to my TODO list, ahead of making a second attempt at making CDT build-configs platform ones.
John
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Belyavsky, Baltasar [bbelyavsky@xxxxxx]
Sent: Tuesday, August 07, 2012 8:55 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] CDT build config references versus Platform project references
The Platform references were already removed from CDT build flow at some point in the past, but that change was reverted because it broke some scenarios.
Take a look at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=291751,
which was reverted because it introduced
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317402.
Another problem is that the indexer still uses the Platform project references – removing the Platform references currently causes the indexer to ignore referenced
projects even if the CDT build-configuration references are in place.
FYI, here is the top-level bugzilla James used to track the project-references work:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309769.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Cortell John-RAT042
Sent: Monday, August 06, 2012 8:33 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] CDT build config references versus Platform project references
Doug,
To my knowledge, the Platform's project references page does nothing for CDT projects and can only serve to confuse the user. I recently opened a bugzilla against the platform as there is no clean way for products (plural) to suppress the platform's properties
page:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385431
We avoid it in CodeWarrior with a hack. We're hoping the platform will eventually give us a proper way to do it.
John
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx]
on behalf of Doug Schaefer [dschaefer@xxxxxxx]
Sent: Thursday, August 02, 2012 11:08 PM
To: CDT General developers list.
Subject: [cdt-dev] CDT build config references versus Platform project references
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?
|