Re: [cdt-dev] building projects prior to a launch

[James Blackburn <jamesblackburn@xxxxxxxxx>]

On 21 May 2010 00:43, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
> So, my suggestion is to simply build the project referenced in the launch
> configuration, and specifically the build configuration specified in the
> launch configuration, and to hell with any projects that such project
> references :-) This until we come up with a way to more precisely tie two
> CDT projects.

Yes, that's the right and simplest thing to do for the moment. I filed bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309126

The main problem is that there's no core.resources provided way of
building references, or knowing that you're being built as a result of
a reference.   So the platform has no consistent way of doing this.
CDT MBS took the approach that the top-level project implicitly builds
the references.  This actually invalidates things like build delta,
but it's what it does...  So MBS + the currently launch does a _lot_
of building.

I think a better solution is to provide a utility class in cdt.core
akin to that can be delegated to by all the places that want to do
build - pressing the build hammer, launches, ISVs - and do the right
thing for our builders. For Helios we could just put in the expedient
fix.

Cheers,
James

>
> A compromise may be to consider that all referenced projects might have
> configurations of the same name, and build the specified configuration where
> available, otherwise whichever one is active for the project. I really don't
> like this since it provides expected behavior for people who use consistent
> configuration names in all their projects, but different behavior for
> others.
>
> Thoughts?
>
> John
>
> [1] See project Properties > Project References
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>