True, but I can always change the "build" to something else if needed
(like a release). 98% of the time using "Build" works just fine. I
think there have been lots of great discussions and suggestions in
this thread that you should be able to find something that works for
you.
I envy the distributed GCC folks who do -j50. ;-)
--
Mike Jackson <www.bluequartz.net>
PS: Had to use an old single CPU PPC the other day.. Painful going
from a Dual Xeon 5500 to a 1.25GHz ppc..
On Dec 3, 2009, at 3:46 PM, Rodolfo Schulz de Lima wrote:
Michael Jackson wrote:
cmake -C ${workspace_loc}/${project_name}/Build -j 16 VERBOSE=1
And the executables (as setup in the Cmake files) are always built
into
Build/Bin.
This way you can only have one build tree per project. One way to
extend
it is to use something like "Build_${build_type}" and set up variables
accordingly. But, IMHO, symlink trees are simpler to work with.
[]s.
rod
PS: I envy your -j16 :)
_______________________________________________
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
_______________________________________________
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