RE: [cdt-dev] How can I properly add an IPathEntry to an ICProject?

["Sennikovsky, Mikhail" <mikhail.sennikovsky@xxxxxxxxx>]

Hi Alain,

I agree with your suggestions. I suppose we should make the path entry
mechanism function in both directions in the MBS for the post-3.0 CDT.
We might also consider some other points where MBS is to be more tightly
integrated with the rest of the CDT.

Thank you,
Mikhail

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alain Magloire
Sent: Thursday, June 23, 2005 11:47 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] How can I properly add an IPathEntry to an
ICProject?

> 
> Hi Devin,
> 
> =20
> 
> The managed build system is not capable of setting the "includePath"
MBS
> option values from the list of the CDT include path entries, but on
the
> contrary MBS automatically add include paths stored in the
"includePath"
> options to the set of project path entries.
> 

Right, and this is something that is bothering me.  We provide an API
that is no tied to any build mechanisms so you can add/remove new
include paths
macros etc and other information.  The MBS never implemented the
extension.
It is to late for the CDT-3.0 but it something I would like to tackle at
one
point, there are too much loose ends and basically no integration of the
MBS to
the rest of CDT, even the UI is different and confusing to the users
when
switching to different builders.

> If I understood you correctly, what you need to do is to add the
Include
> path value to the "includePath" option of your compiler tool rather
than
> adding the path entry directly. This will make the include paths you
> specified in the option be added to the tool invocation command while
> generating the makefile. The values you specified will be
automatically
> translated to the path entries and added to the list of project path
> entries, so you don't need to add the path entry to the project
> directly, because MBS will do it for you.
> 

Agreed.  But the other way should have work as well doing thing this
way make you dependent on all of the internals of one builder.
IMO, doing this:
 CoreModel.setNewPathEntries(...);

Should work and hide the kitchen work.


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev