Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: RE: [cdt-dev] rm: cannot lstat - problem while cleaning duringbuild

Hi Aparna,

 

>One point to note: When I say ‘clean’ from Project menu, the .o files get deleted.

This is because MBS programmatically removes the top builder directory during clean instead of invoking the builder.

 

>The .o files are located in (<project_path>/<configuration_name> path.

The error message you posted recently says rm can not find the a.o file. Is it really in your builder CWD? Try launching the make –k clean command from the command line from the <project_path>/<config_name> directory. Does it works?

You might also want to open the generated makefiles and see what is wrong there, e.g. whether the clean rule is defined appropriately, etc.

I have noticed that your builder definition differs from the one defined for the standard gnu make builder (see plugin.xml file for the org.eclipse.cdt.managedbuilder.gnu.ui plug-in) are using some custom builder? You said you have added cygwin/bin directory to your path. Are you sure that make –k clean invokes the “right” make you need, (not cygwin’s in case of using the custom builder), what does “which make” command say? Are you sure you are using the “right” rm? What does “which rm” command say?

 

Regards,

Mikhail

 

 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Aparna Argade
Sent: Thursday, December 01, 2005 3:36 PM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: RE: [cdt-dev] rm: cannot lstat - problem while cleaning duringbuild

 

Hi,

One point to note: When I say ‘clean’ from Project menu, the .o files get deleted.

But they don’t get deleted through rm command during build project phase.

Regards,

Aparna

 

 


From: Aparna Argade
Sent: Thursday, December 01, 2005 5:59 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] rm: cannot lstat - problem while cleaning during build

 

Hi Mikhail,

The .o files are located in (<project_path>/<configuration_name> path.

Regards,

Aparna


Back to the top