Databases
StackOverflow2013
Postsdbo
POEclipse CDT not building project on header file change
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse CDT not building project on header file change
    text
    copied!<p>I have Eclipse Platform 3.7.2 and CDT 8.0.2.</p> <p>When I want to do 'Build All' headers from other workspace projects are not counted as dependencies, and nothing is rebuilt.</p> <p>I have a hello world application and a static library project. The static library is set as a reference in Project Properties -> c/c++ general -> Paths and SYmbols -> References tab -> checked 'Active'. That's the only setting I changed.</p> <p>By the way, It totally beats me why Eclipse has an additional "Project References" top-level item under Project Properties.</p> <p>Anyway, I tried both the External Builder (which gets selected by default on project creation) and the INternal Builder, also coupled with combinations of the global setting 'Preferences -> c++ -> Build -> Build configurations only when there are Eclipse resource changes........'</p> <p>Thanks for any thoughts on this.</p> <p>Update: This is the console output when building dependent project Proj2 (Proj1 is the lib). 'make all' is called but it merely re-links, it doesn't recompile Main.cpp as it should. Anyone out there familiar with eclipse-generated makefiles? Thanks again.</p> <pre><code>**** Build of configuration Debug for project Proj2 **** make all Building target: Proj2 Invoking: Cross G++ Linker g++ -L"/home/user/.eclipse-workspace/Proj1/Debug" -o "Proj2" ./Main.o -lProj1 Finished building target: Proj2 **** Build Finished **** </code></pre> <p>Edit: This is 1.5 years old already, wanted to add that an Eclipse bug had been filed for this: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=375800">https://bugs.eclipse.org/bugs/show_bug.cgi?id=375800</a></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload