Re: [CMake] Support for multiple components in cpack (reloaded)

[Alexander Neundorf]

On Sunday 22 August 2010, Eric Noulard wrote:
...
> CPack is not aware **AT ALL** of subprojects :-(
>
> It's even worse, since CPack is not meant to be included more than once
> in the same tree.
> In fact you already know that because you are the reporter of this:
> http://public.kitware.com/Bug/view.php?id=10751
>
> A related discussion on the ML:
> http://www.cmake.org/pipermail/cmake/2010-August/038648.html
>
> So I would say, unless I misunderstood something,
> that **currently** you CAN NOT use "subproject" to do any grouping with
> CPack. If any subproject do include(CPack) while your toplevel project does
> it as well, you'll get unexpected behavior.
> The most probable consequence is that is you call "make package" in the
> toplevel project you'll get a source package instead of a binary package
> :-)
>
> What you CAN ALREADY do is to use your toplevel project to build a package
> which contains all subprojects. You can even use component in the
> subproject(s) it will
> work as expected.
>
> If we want to be able to include(CPack) several times, many thing
> should be changed

This would probably make cpack usable for KDE, where we have a lot of apps 
(subprojects) inside one svn tree :-)

> and we should specify the expected behavior very precisely, I do not
> think it's as easy
> as it may seems. Definitely on my workplan now :-(

Cool, thanks for your efforts :-) 

Alex
___
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

Re: [CMake] Is there a tool pretty much like cmake for Java?

[Alexander Neundorf]

On Saturday 21 August 2010, Mr Shore wrote:
> Hi there
>
> The best building tool for Java I know so far seems to be maven,
>
> but it still doesn't give so much flexibility as cmake at all!
>
> Anyone knows a cmake-alike tool for java?

CMake "supports" Java, but that support is ... needs some work, there are some 
issues (I think this had to do with the location of the compiled files and 
the java packages or something).
I assume patches to improve the situation would be accepted :-)

Alex
___
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

Re: [CMake] How to invoke 64 bit cmd.exe from cmake script on Windows 7 (x64).

[Rolf Eike Beer]

Am Sunday 22 August 2010 schrieb David Cole:
> I do something like this in a batch file to guarantee running 32-bit from a
> 64-bit command prompt:
> 
> @rem  Workaround allows msys/cygwin rxvt to run on Windows x64
> 
> @rem(SysWOW64\cmd.exe runs as 32-bit)
> 
> @rem
> 
> @if "%PROCESSOR_ARCHITECTURE%" equ "AMD64" (
> 
>   @"%WINDIR%\SysWOW64\cmd.exe" /c ""%~f0" %*"
> 
>   @exit /b 0
> 
> )

You know about "@echo off"? That saves the @ before every line.

Eike


signature.asc
Description: This is a digitally signed message part.
___
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

Re: [CMake] How to invoke 64 bit cmd.exe from cmake script on Windows 7 (x64).

[David Cole]

I do something like this in a batch file to guarantee running 32-bit from a
64-bit command prompt:

@rem  Workaround allows msys/cygwin rxvt to run on Windows x64

@rem(SysWOW64\cmd.exe runs as 32-bit)

@rem

@if "%PROCESSOR_ARCHITECTURE%" equ "AMD64" (

  @"%WINDIR%\SysWOW64\cmd.exe" /c ""%~f0" %*"

  @exit /b 0

)

What you're asking for is the inverse: running a 64-bit program from a
32-bit program. I'm not sure what the right file reference to use is to do
this, but I'm sure you can do it. If nobody else replies again to this
thread sooner, I'll try to figure out the right invocation and pass it
along.

Good luck,
David


On Sun, Aug 22, 2010 at 2:36 PM, Alexander Tarnopolsky <
alexander.tarnopol...@pdgm.com> wrote:

>
> Hi,
>
> I'm trying to invoke an interactive shell from a cmake script using the
> following:
>
> execute_process (COMMAND ${SHELL} ${ARGS})
>
> And the 32bit cmd.exe is invoked on "Windows 7 x64" (since the cmake
> itself runs in 32bit environment).
> But I'm interested in 64bit cmd.exe.
> Is there a way to invoke it from cmake?
>
> Thanks in advance for your comments.
>
> Regards,
> Alexander Tarnopolsky
> Build Manager, Epos
>
> alexander.tarnopol...@pdgm.com
> www.pdgm.com
>
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
> Of Arnaud GELAS
> Sent: Friday, August 20, 2010 7:19 PM
> To: cmake@cmake.org
> Subject: [CMake] TRY_COMPILE and -Werror
>
>
>  Hi all,
>
> I would like to check if one piece of code generates a warning or not
> (about a deprecated method). I want to use TRY_COMPILE and adds -Werror
> to gcc flags.
>
> I have tried the following:
>
> TRY_COMPILE(VTK_FFMPEG_GUESSFORMAT
>  ${VTK_BINARY_DIR}/CMakeTmp
>  ${VTK_CMAKE_DIR}/vtkFFMPEGTestGuessFormat.cxx
>  CMAKE_FLAGS
> "-DINCLUDE_DIRECTORIES:STRING=${FFMPEG_INCLUDE_DIR}"
>-DCOMPILE_DEFINITIONS:STRING=-D${VTK_FFMPEG_CDEFS}
>-DCOMPILE_DEFINITIONS:STRING=-D__STDC_CONSTANT_MACROS
>   "-DLINK_LIBRARIES:STRING=${FFMPEG_avformat_LIBRARY}"
>   "-DCMAKE_CXX_FLAGS:STRING=-Werror"
>  OUTPUT_VARIABLE OUTPUT)
>
> But VTK_FFMPEG_GUESSFORMAT is still true...
>
> Any idea?
>
> Thanks,
> Arnaud
> ___
> 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
>
___
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

Re: [CMake] try_run understanding.

[Alexander Neundorf]

On Friday 20 August 2010, Ricardo Tiago wrote:
> Hi all,
>
> How can I use try_run with multiple source files?
>
> Something like: gcc  foo.c foo_fn.c -o newfoo
>
> So far I've came up with the following..
>
> try_run (RUN_RESULT_VAR COMPILE_RESULT_VAR
> ${CMAKE_BINARY_DIR}
> ${CMAKE_CURRENT_SOURCE_DIR}/foodir/foo.c
> CMAKE_FLAGS
>  
> -DINCLUDE_DIRECTORIES:STRING=${CMAKE_CURRENT_SOURCE_DIR}/foodir/
> COMPILE_OUTPUT_VARIABLE COMPILE_OUTPUT_VAR)

try_run() and try_compile() are quite low level.
Did you have a look at the check_c/cxx_source_runs() macro coming with cmake ?
This is recommended in general.

Alex
___
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

Re: [CMake] How to invoke 64 bit cmd.exe from cmake script on Windows 7 (x64).

[Tyler Roscoe]

On Sun, Aug 22, 2010 at 07:36:21PM +0100, Alexander Tarnopolsky wrote:
> I'm trying to invoke an interactive shell from a cmake script using the
> following: 
> 
> execute_process (COMMAND ${SHELL} ${ARGS})
> 
> And the 32bit cmd.exe is invoked on "Windows 7 x64" (since the cmake
> itself runs in 32bit environment). 
> But I'm interested in 64bit cmd.exe.
> Is there a way to invoke it from cmake?

Where is ${SHELL} defined? What is its value?

I suspect you could use find_program() with appropriate arguments to
specify that you want the 64-bit cmd.exe.

tyler
___
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

[CMake] How to invoke 64 bit cmd.exe from cmake script on Windows 7 (x64).

[Alexander Tarnopolsky]

Hi,

I'm trying to invoke an interactive shell from a cmake script using the
following: 

execute_process (COMMAND ${SHELL} ${ARGS})

And the 32bit cmd.exe is invoked on "Windows 7 x64" (since the cmake
itself runs in 32bit environment). 
But I'm interested in 64bit cmd.exe.
Is there a way to invoke it from cmake?

Thanks in advance for your comments.
 
Regards,
Alexander Tarnopolsky 
Build Manager, Epos
 
alexander.tarnopol...@pdgm.com
www.pdgm.com

-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Arnaud GELAS
Sent: Friday, August 20, 2010 7:19 PM
To: cmake@cmake.org
Subject: [CMake] TRY_COMPILE and -Werror


  Hi all,

I would like to check if one piece of code generates a warning or not 
(about a deprecated method). I want to use TRY_COMPILE and adds -Werror 
to gcc flags.

I have tried the following:

TRY_COMPILE(VTK_FFMPEG_GUESSFORMAT
  ${VTK_BINARY_DIR}/CMakeTmp
  ${VTK_CMAKE_DIR}/vtkFFMPEGTestGuessFormat.cxx
  CMAKE_FLAGS
"-DINCLUDE_DIRECTORIES:STRING=${FFMPEG_INCLUDE_DIR}"
-DCOMPILE_DEFINITIONS:STRING=-D${VTK_FFMPEG_CDEFS}
-DCOMPILE_DEFINITIONS:STRING=-D__STDC_CONSTANT_MACROS
   "-DLINK_LIBRARIES:STRING=${FFMPEG_avformat_LIBRARY}"
   "-DCMAKE_CXX_FLAGS:STRING=-Werror"
  OUTPUT_VARIABLE OUTPUT)

But VTK_FFMPEG_GUESSFORMAT is still true...

Any idea?

Thanks,
Arnaud
___
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

Re: [CMake] How to add CORBA idl files to Visual Studio source group

[Michael Hertling]

On 08/22/2010 05:21 PM, Claus Klein wrote:
> Ok,
> I found the solution myself; I have to add:
> set_source_files_properties(interface1.idl PROPERTIES HEADER_FILE_ONLY  
> TRUE)
> 
> But I do not understand why this is needed with VS2005?

See  and
 for information.

> By the way, the REGULAR_EXPRESSION does not work?
> 
> I have to use the FILES parameter to group the idl files!
> That is really strange.

Try ".*\\.idl" instead of "*.idl" since the latter is a typical
globbing expression but no valid regular expression for CMake.

Regards,

Michael

> On 19.08.2010, at 22:59, Claus Klein wrote:
> 
>> Hi,
>>
>> I have a project with CORBA idl files, which will be compiled with a  
>> tao idl compiler to source and header files via a:
>>
>>  add_custom_command(OUTPUT output1 [output2 ...] ...)
>>
>> I defined a source group with:
>>
>>  source_group(idlfiles REGULAR_EXPRESSION *.idl)
>>
>> The generated source are added  with ohter source to build libs  and  
>> executables for different subsystems:
>>
>>   add_library(interfacelib1 interface1.idl interface1C.cpp   ).
>>
>> I add the idl files too. The idlfiles group was filled with my idl  
>> files. OK, that was my intention.
>> That works with header files, but not with idl files:
>>
>> When I compile the project, there are build error because the VS2005  
>> does not know who to compile the .idl files?
>>
>> All works fine without the idl file in the source list of the libs.  
>> But can't see the idl file in the VS project.
>>
>> Is there an other way to get the idl files to a source group under  
>> there library projects?
>>
>>
>> //regards
>> Claus
___
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

Re: [CMake] Support for multiple components in cpack (reloaded)

[Eric Noulard]

2010/8/22 Eric Noulard :
> 2010/8/21 Clinton Stimpson :
>>
>> I wondered if one would typically use groups if their project contained sub 
>> projects, and the sub projects had different conventions for the component 
>> names.
>
> I do not usually work with sub-project and I must admit I don't even know
> how CPack behave for project with sub-project(s). I'll try in order to observe
> the current behavior.

Ok now I did some testing regarding CPack and subproject(s).
>From my testing and my thinking the conclusion is

CPack is not aware **AT ALL** of subprojects :-(

It's even worse, since CPack is not meant to be included more than once
in the same tree.
In fact you already know that because you are the reporter of this:
http://public.kitware.com/Bug/view.php?id=10751

A related discussion on the ML:
http://www.cmake.org/pipermail/cmake/2010-August/038648.html

So I would say, unless I misunderstood something,
that **currently** you CAN NOT use "subproject" to do any grouping with CPack.
If any subproject do include(CPack) while your toplevel project does
it as well, you'll get unexpected behavior.
The most probable consequence is that is you call "make package" in the toplevel
project you'll get a source package instead of a binary package :-)

What you CAN ALREADY do is to use your toplevel project to build a package which
contains all subprojects. You can even use component in the
subproject(s) it will
work as expected.

If we want to be able to include(CPack) several times, many thing
should be changed
and we should specify the expected behavior very precisely, I do not
think it's as easy
as it may seems. Definitely on my workplan now :-(


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
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

Re: [CMake] Support for multiple components in cpack (reloaded)

[Eric Noulard]

2010/8/22 Eric Noulard :
> 2010/8/22 Rolf Eike Beer :
>> Am Saturday 21 August 2010 schrieb Eric Noulard:
>>
>>> They change the number and the contents of the generated packages:
>>>     3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
>>>           means you want to get a single package whose content
>>>           is the merge of all components GROUPS
>>>
>>>     3.b) CPACK_COMPONENTS_ALL_IN_ONE_PACKAGE=1
>>>            means you want to get a single package whose content
>>>            is the merge of all COMPONENTS
>>>
>>>      3.c) CPACK_COMPONENTS_IGNORE_GROUPS
>>>            means you want to get 1 package per COMPONENT
>>>            (the default is 1 package per GROUP)
>>
>> AFAICS those are exlusive, so why don't you use a single variable with 3
>> different values that prints a big fat warning if it is set to anything else 
>> to
>> make error detection easier?
>
> Yes they are exclusive.
> I think the main reason for separate variables is because its "usually" the 
> way
> it works with CPack/CMake there are more toggle var 0/1 than switches
> values vars.
>
> But this is a good point what do you suggest:
>
> CPACK_COMPONENTS_GROUPING
> with possible values:
>   ALL_GROUP_IN_ONE
>   ALL_COMPONENT_IN_ONE
>   IGNORE_GROUP

Hi Rolf,

I do update my patchset with your proposal now you can

cpack  -D CPACK_COMPONENTS_GROUPING= -G 

if the  is not recognized you'll get a warning.
the previous 3.a/3.b/3.c variables may be used too.

We may keep them both or decide what is the better way to go after some tests.

The new patch
 0003-CPackArchiveGenerator-improve-usability-and-robustne.patch
is on the bug page:
http://public.kitware.com/Bug/view.php?id=10736

Github repo has been updated too:
http://github.com/TheErk/CMake/tree/CPackArchiveGenerator-ComponentSupport

The patch also fix the case where components are defined but
no component groups are defined, in this case we build 1 package per component
instead of 1 package per group.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
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

Re: [CMake] Windows debugger command project settings

[Mike McQuaid]

On 20 Aug 2010, at 21:48, Ryan Pavlik wrote:

> You might consider using my CreateLaunchers cmake module that will set up the 
> debugger for you to add whatever directories you like to the PATH (on 
> windows) so that it can find the dynamic libraries.  I haven't tried it in 
> the case that the libraries are built in the same project - you'd probably 
> have to do a little work to figure out where they were going to land to be 
> able to pass that path - but it works great for successfully finding 
> third-party libraries.  (In a pinch, you could build the install target, then 
> run the regular one, having put the install location of the libraries into 
> your RUNTIME_LIBRARY_DIRS)

Another alternative would be to use InstallRequiredSystemLibraries, 
BundleUtilities and/or GetPrerequisites.

--
Cheers,
Mike McQuaid
http://mikemcquaid.com

___
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

Re: [CMake] How to add CORBA idl files to Visual Studio source group

[Claus Klein]

Ok,
I found the solution myself; I have to add:
set_source_files_properties(interface1.idl PROPERTIES HEADER_FILE_ONLY  
TRUE)


But I do not understand why this is needed with VS2005?
By the way, the REGULAR_EXPRESSION does not work?

I have to use the FILES parameter to group the idl files!
That is really strange.

Claus

On 19.08.2010, at 22:59, Claus Klein wrote:


Hi,

I have a project with CORBA idl files, which will be compiled with a  
tao idl compiler to source and header files via a:


add_custom_command(OUTPUT output1 [output2 ...] ...)

I defined a source group with:

source_group(idlfiles REGULAR_EXPRESSION *.idl)

The generated source are added  with ohter source to build libs  and  
executables for different subsystems:


 add_library(interfacelib1 interface1.idl interface1C.cpp   ).

I add the idl files too. The idlfiles group was filled with my idl  
files. OK, that was my intention.

That works with header files, but not with idl files:

When I compile the project, there are build error because the VS2005  
does not know who to compile the .idl files?


All works fine without the idl file in the source list of the libs.  
But can't see the idl file in the VS project.


Is there an other way to get the idl files to a source group under  
there library projects?



//regards
Claus
___
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

Re: [CMake] Support for multiple components in cpack (reloaded)

[Eric Noulard]

2010/8/21 Clinton Stimpson :
>
> I wondered if one would typically use groups if their project contained sub 
> projects, and the sub projects had different conventions for the component 
> names.

I do not usually work with sub-project and I must admit I don't even know
how CPack behave for project with sub-project. I'll try in order to observe
the current behavior.

> Would grouping be a way to overcome that?
> It doesn't seem so, because in the wiki, the nsis example shows a hierarchy 
> of components.
> Or does one just make a common display name for multiple components?

I think component introduction in CPack was meant to bring a mean for:
building a single installer which contains both mandatory and optional part
**in the same package**.

Grouping seem to be there to ease display and "group" selection because
you can tick/untick a group.

Now I think may be you could achieve the same "grouping" effect by using
subproject but:
 1) the devel/runtime grouping does not fall in this category
 2) the component thing is more flexible because you can throw any
 part of your project inside any component whereas using sub-project
 enforce some structural inclusion.

So I think that some sub-project may replace grouping but not all.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
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

Re: [CMake] Support for multiple components in cpack (reloaded)

[Eric Noulard]

2010/8/22 Rolf Eike Beer :
> Am Saturday 21 August 2010 schrieb Eric Noulard:
>
>> They change the number and the contents of the generated packages:
>>     3.a) CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE=1
>>           means you want to get a single package whose content
>>           is the merge of all components GROUPS
>>
>>     3.b) CPACK_COMPONENTS_ALL_IN_ONE_PACKAGE=1
>>            means you want to get a single package whose content
>>            is the merge of all COMPONENTS
>>
>>      3.c) CPACK_COMPONENTS_IGNORE_GROUPS
>>            means you want to get 1 package per COMPONENT
>>            (the default is 1 package per GROUP)
>
> AFAICS those are exlusive, so why don't you use a single variable with 3
> different values that prints a big fat warning if it is set to anything else 
> to
> make error detection easier?

Yes they are exclusive.
I think the main reason for separate variables is because its "usually" the way
it works with CPack/CMake there are more toggle var 0/1 than switches
values vars.

But this is a good point what do you suggest:

CPACK_COMPONENTS_GROUPING
with possible values:
   ALL_GROUP_IN_ONE
   ALL_COMPONENT_IN_ONE
   IGNORE_GROUP

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
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