RE: [cdt-dev] Build-command unreliable

["Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>]

I couldn't find any other defects, but I'm pretty sure that I saw some discussion about this somewhere (probably on a mailing list, either cdt-* or platform-core-dev).  Basically, if Eclipse does not think that any resources have changed in the project or its pre-requisite projects, then no build is performed.  This is done in the "platform", so the CDT builder can't change this behavior.  The most common cause for this either changing the project files outside of Eclipse or changing non-project files that affect the build (system-wide libraries, headers, etc.).  For the former, you can "refresh" the project (Eclipse will then "notice" your changes).  For the later, the only recourse I know of is to make a "trivial" change to the project, so that Eclipse will see a change and call make.  You can also "clean" the projects, but that has obvious disadvantages.

I think there was also some discussion with the platform guys about allowing builders like the CDT that use external programs to override some of the "java-centric" builder behaviors (which may include this).  I'm not sure where those ended up.

  Jeremiah

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett, Norbert
Sent: Tuesday, September 06, 2005 4:17 AM
To: CDT General developers list.
Subject: [cdt-dev] Build-command unreliable


Hello folks,

this is a phenomenon that I and other colleagues are encountering: The "Build" commands do not seem to work reliably. This goes for "Build all" and "Build project", for Linux and Windows, for managed and standard C/C++ projects. In many cases eclipse seems to think that no resources were changed (though there were, in fact, some changes) and therefore no build process is started. So make does not even get the chance to figure out on its own whether any changes need to be processed.

I looked through the bugzilla and found one problem report which seems related (102550) and which has not yet been treated. In our team we have not yet been able to create reproducible situations so it is too early to create a bug report, but still this behavior is pretty irritating.

Is this problem known? Can anybody point me to other bug reports? 

Thanks for your effort,


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