[CMake] empty string and cmake_parse_arguments

2016-01-09 Thread Burlen Loring
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.


Burlen
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


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

2016-01-09 Thread Konstantin Podsvirov
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)
project(test)

set(CPACK_PACKAGE_NAME Hello)
set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Hello world using IFW")
set(CPACK_PACKAGE_VERSION "1.0.0")
set(CPACK_GENERATOR "IFW")
set(CPACK_COMPONENTS_GROUPING "IGNORE")

set(PLUGINS one two)

foreach (plugin ${PLUGINS})
 install(
 FILES ${plugin}.js
 COMPONENT plugin_${plugin}
 DESTINATION plugins
 )

 list(APPEND CPACK_COMPONENTS_ALL plugin_${plugin})
endforeach ()

include(CPack)
include(CPackIFW)

cpack_add_component_group(plugins)

foreach (plugin ${PLUGINS})
 cpack_add_component(
 plugin_${plugin}
 DISPLAY_NAME "${plugin}"
 DESCRIPTION "Install ${plugin}.js"
 GROUP plugins
 )
endforeach ()

(not tested, but should work :-)

In this embodiment do not need to create a dummy group.
Also all the plugins are selected by default. If you want you can
to indicate return putting in DISABLED when the component is added.

If you have more questions, ask. I'll try to answer.

--
Regards,
Konstantin Podsvirov
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


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

2016-01-09 Thread Alexander Neundorf
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 the root of the
> build tree to invoke a full build in parallel, but I see no way of doing
> that from the Code Blocks IDE.

Oops, sorry, that's not implemented for C::B.

Alex

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


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

2016-01-09 Thread Dimitri Kaparis
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 way of doing
that from the Code Blocks IDE.

In the "Project build options" window, under "Make commands" tab, there is
a box to specify a "Build project/target" command, where I can add -j
switch to make. But that box is only editable for individual executable and
library subprojects, while for virtual CMake-generated targets, such as
"all", it is disabled.

Any ideas?

Regards,
Dimitri
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Make CMAKE_EXPORT_COMPILE_COMMANDS not default?

2016-01-09 Thread René J . V . Bertin
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 default, one that apparently didn't come up.
IDEs like KDevelop and QtCreator use this option to know the layout/contents of 
a project. They will add it to the cmake invocation when you create a new build 
directory for said project. However, they can also be pointed to an already 
existing build directory, in which case it'd be preferable if they didn't have 
to run cmake again (neither IDE has the option to run cmake under the kind of 
strictly controlled environment that might be required to configure it "just 
right").

Regards,
René

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake