[CMake] Code::blocks: parallel build from IDE

Greetings, I'm using the "CodeBlocks - Unix Makefiles" generator under linux to create a build tree for my project consisting of multiple executables and libraries. >From the command line, I could use make -jN switch from the root of the build tree to invoke a full build in parallel, but I see no

[CMake] [Re] How to select components by default using CPack ?

Hi David! I found your letter here: http://public.kitware.com/pipermail/cmake/2015-December/062188.html Earlier I was not subscribed to the CMake Users. I see that you try to use IFW generator. Can offer you the following variant of the script: cmake_minimum_required(VERSION 3.2)

[cmake-developers] [CMake 0015906]: With Microsoft Visual Studio CMake should use the C++ compiler for C files, if C standard >= C99 is set

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=15906 == Reported By:Jan Henke Assigned To:

Re: [CMake] Code::blocks: parallel build from IDE

On Saturday, January 09, 2016 12:27:48 Dimitri Kaparis wrote: > Greetings, > > I'm using the "CodeBlocks - Unix Makefiles" generator under linux to create > a build tree for my project consisting of multiple executables and > libraries. > From the command line, I could use make -jN switch from

[CMake] empty string and cmake_parse_arguments

Is it possible to pass "" (an empty string) through cmake_parse_arguments? I'm using cmake 3.4.0. I found much discussion of a patch to do this in a thread on the cmake developer list. however, cmake_parse_arguments still eats the "", and I am finding no official documentation about it.

[Cmake-commits] CMake branch, master, updated. v3.4.1-795-g7a45d91

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20160109) +set(CMake_VERSION_PATCH 20160110) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Make CMAKE_EXPORT_COMPILE_COMMANDS not default?

Hello, Sorry for reviving an old thread (https://cmake.org/pipermail/cmake/2013-December/056517.html) but it seems to have died without a proper answer, at least one that I could find. I'd like to offer an additional reason why CMAKE_EXPORT_COMPILE_COMMANDS would be beneficial if on by