Note that there are some explanatory texts on larger screens.

plurals
  1. POeclipse CDT: rebuilding a dependent project
    primarykey
    data
    text
    <p>I'm working on a C++ project with eclipse Indigo + CDT running on linux</p> <p>It's made of a project for a library, and a project with unit tests for this library.<br> Obviously the second project depends on the first one.<br> Both projects use the external builder</p> <p>But when I modify a header of the first project it does not rebuild the test project. And I can't make it do it... It'll just re-link the second project, even though the header is included in the test project. This is very annoying because I often have working builds while working on the library, then at some point I do a full rebuild and I see a load of errors, on stuff I did 30 minutes ago!</p> <p>example output of the CDT Global Build Console:</p> <pre><code>**** Build of configuration Debug for project libxxx **** make -j all Building file: ../foo.cpp Invoking: GCC C++ Compiler ccache g++ -I"/home/foke/workspaces/cpp/libxxx/include" -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"foo.d" -MT"foo.d" -o "foo.o" "../foo.cpp" Finished building: ../foo.cpp Building target: libxxx.a Invoking: GCC Archiver ar -r "libxxx.a" ./foo.o ./src/yyy.o ./src/detail/zzz.o ar: creating libxxx.a Finished building target: libxxx.a **** Build Finished **** **** Build of configuration Debug for project libxxx_tests **** make -k -j all Building target: libxxx_tests Invoking: Cross G++ Linker g++ -L"/home/foke/workspaces/cpp/libxxx/Debug" -o "libxxx_tests" ./main.o ./aaa.o ./tests/bbb.o ./tests/ccc.o ./tests/ddd.o -lboost_unit_test_framework -lxxx Finished building target: libxxx_tests **** Build Finished **** </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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