From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Canaye, Kurvin
Sent: Monday, September 10, 2007 6:45
PM
To: CDT General developers list.
Subject: [cdt-dev] Problems with migration
of MBS from CDT 3.3 to CDT4.0
in view of the release of the Topcased C ide at the end of this month, we are
migrating our work from CDT 3.3 to CDT 4.0. Our ide is based on CDT and we
have extended the
org.eclipse.cdt.managedbuilder.core.buildDefinitions
extension point and we have a custon made makefile
generator.
Under CDT 3.3 all worked fine.
However with CDT 4.0, the makefile is generated but it is never called. In
the class implementing the IManagedBuilderMakefileGenerator interface, the
getBuildWorkingDir() method returns a path relative to the project containing
the makefile (TWP4C/config) and the getMakefileName() method returns the
name of the makefile (Makefile).
<builder
arguments="-r
-S"
buildfileGenerator="buildProcess.core.internal.cdtLink.CDTMakefileGenerator"
cleanBuildTarget="gmake
clean"
command="gmake"
id="Topcased_wp4_c.builder"
isAbstract="false"
name="topcased wp4 c
builder"
supportsManagedBuild="true">
</builder>
We
could find no relevent information to this from the "Migrating your tool-chain
integration to CDT 4.0" document nor in the new MBS
Extensibility Document.
Can
anyone please help us on this.
Thanking you in
advance.
Kurvin
Canaye
..........................................................
Cordialement/Kind
regards
Kurvin
Canaye
Siemens VDO Automotive
AG
SV PED T SW
EE
Toulouse
France
E-Mail: kurvin.canaye@xxxxxxxxxxx
Internet: http://www.siemensvdo.com