Hi Michael > Ok, to clear things up: <snip> > I hope you get the idea.
Thanks very much, I think I get it now! I have implemented an out-of-source build tree for our project, as you suggested, and it is building fine. I'm wondering what my co-developers will think of it. It is usual for us to work in the source directory of a certain library, make modifications and then type make to build just that library. With this out-of-source build tree it will be necessary to hop from the source dir to the build tree, type make there and let the entire project build (i.e. other libraries and the executable as well). Am I understanding correctly? > So, I usually have something like this: > > ~/Projects/super_duper <--- source tree > ~/Projects/super_duper-build/debug <--- debugging build tree > ~/Projects/super_duper-build/release <--- release build tree > ~/Projects/super_duper-build/dashboards <--- parent directory for dashboard > builds Do you usually let the libraries and executables live in the subdirectories where CMake would naturally put them? For example, some of my build artifacts would be: super_duper-build/release/Kernel/libKernel.a super_duper-build/release/VersionInfo/versionInfo Or would good practice me to put them somewhere more obvious? Best regards David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
