Hi Gerrit,
The programmatic clean logic recides in the void
org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder.clean(CfgBuildInfo
bInfo, IProgressMonitor monitor) throws CoreException
method. The only way to extend/replace it
is replacing the project builder (void
org.eclipse.cdt.managedbuilder.internal.core.CommonBuilder).
Why does specifying the clean command and target
is not suitable for you?
Mikhail
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Gerrit Brehmer
Sent: Wednesday, September 12,
2007 5:41 PM
To: CDT
General developers list.
Subject: Re: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
could you please tell me where the implementation of the
programmatically clean is? Because i want to extend this implementation (must
cleanup a programmatically created directory and extending the makefile clean
target only helps under linux)
Thanks,
Gerrit
----- Original Message
----
From: "Sennikovsky, Mikhail" <mikhail.sennikovsky@xxxxxxxxx>
To: CDT General developers list.
<cdt-dev@xxxxxxxxxxx>
Sent: Wednesday, September 12, 2007 1:22:40 PM
Subject: RE: [cdt-dev] Problems with migration of MBS from CDT 3.3 to CDT4.0
Hi Curvin,
You are right, the clean is performed
programmatically for Managed projects. This was done a while ago in the 3.x
times due to the bug with the .d files being corrupted in case of a build
cancel.
I guess we could change the clean behavior
to make the clean via builder invocation be tried first and in case it fails,
the programmatic clean is executed. Could you raise a bugzilla regarding this?
Thanks,
Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Canaye, Kurvin
Sent: Tuesday, September 11, 2007
4:40 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Hi Mikhail,
with this CDT build the makefile is executed. This is nice.
I would like to ask for a precison
however on the clean. The makefile contains a clean section with the
appropriate operations to carry out. The cleanBuildTarget attribute of our
builder, is set to gmake clean. When I make a clean on the project,
only the working directory is deleted. Is there a way of getting the clean
section of the makefile to be executed?
Thanks,
Kurvin
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Sent: Tuesday, September 11, 2007
10:49 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Hi Kurvin,
The ..0907.. build does not contain the
fix. The fix should be included in the builds starting today’s one.
Try the I200709110100 one and let me know if it does not
work for you.
Thanks,
Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Canaye, Kurvin
Sent: Tuesday, September 11, 2007
12:43 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Hi Mikhail,
I've taken CDT build 4.0.1.200709070100; RC0. I still cant get my
Makefile to be executed. In CDT 3.3 when I launched a build, the
getBuildWorkingDir() and the getMakefileName() form the class implementing
IManagedBuilderMakefileGenerator were called.(These methods I guess were what
allowed CDT to know where my Makefile was located and the name of the file; am
I wrong? ) With the actual CDT build I have, these methods are not
called and I get Exec error: The name of the directory is incorrect.
Is this the normal functioning? If yes how
do I get CDT to execute the builder command and clean command on the generated
Makefile?
Thanks,
Kurvin
..........................................................
Cordialement/Kind regards
Kurvin Canaye
Siemens VDO Automotive AG
SV PED T SW EE
Toulouse
France
E-Mail: kurvin.canaye@xxxxxxxxxxx
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Sent: Monday, September 10, 2007
6:32 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Thanks Kurvin,
The bug should be fixed already.. Please
give it a try and let me know if it does not work as expected.
Thanks,
Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Canaye, Kurvin
Sent: Monday, September 10, 2007
7:37 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Hi,
I rose a bug relative to this
problem. See bug 202805.
Hope I've done things right. If you can't find the bug tell me I'll make
a new entry.
..........................................................
Cordialement/Kind regards
Kurvin Canaye
Siemens VDO Automotive AG
SV PED T SW EE
Toulouse
France
E-Mail: kurvin.canaye@xxxxxxxxxxx
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Sennikovsky, Mikhail
Sent: Monday, September 10, 2007
4:55 PM
To: CDT
General developers list.
Subject: RE: [cdt-dev] Problems
with migration of MBS from CDT 3.3 to CDT4.0
Hi,
This seems like a bug.. Please raise a
bugzilla and I’ll fix the problem ASAP so that the fix is included in the CDT
4.0.1.
Mikhail
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
org.eclipse.cdt.managedbuilder.core.buildDefinitions extension
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).
Below is the plug-in.xml part of our builder
<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
-------------------------------------------------------------------- Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
Fussy? Opinionated? Impossible to please? Perfect. Join
Yahoo!'s user panel and lay it on us.
--------------------------------------------------------------------
Closed Joint Stock Company Intel A/O
Registered legal address: 125252, Moscow, Russian Federation,
Chapayevsky Per, 14.
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
|