<div dir="ltr">Hi,<br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/11 Mark Stijnman <span dir="ltr"><<a href="mailto:mark.stijnman@gmail.com" target="_blank">mark.stijnman@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On Tue, Nov 5, 2013 at 12:11 PM, Alexander Broekhuis<br>
<br>
<br>
</div></div>The easiest way I know is to use CPACK_COMPONENTS_ALL, which is what I<br>
use to package subsets of my components.<br></blockquote><div><br></div><div>I now solved it using CPACK_INSTALL_CMAKE_PROJECTS and populating it with all components to be installed. Not sure how CPACK_COMPONENTS_ALL is different, but will take a look.</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I don't currently use grouping, but if I would, I would create<br>
something like an add_component_to_group(compname, groupname)<br>
function, that you can call for every component when you first define<br>
it (or add a GROUP parameter it to my define_package_component()<br>
function). In addition to setting<br>
PACK_COMPONENT_${compname_uppercase}_GROUP to ${groupname}, it should<br>
append ${compname} to a (global) package_group_${groupname}_components<br>
list variable. Then populate the CPACK_COMPONENTS_ALL list by<br>
iterating over your list of required groups, and for each group name,<br>
append ${package_group_${groupname}_components}.</blockquote><div><br></div><div>In my custom Macros I do more or less the same. I append all components to a cached internal variable. Then later on I create the CPack configuration with this information. I guess you mean the same when talking about a global variable? Or is there a different more simpler way without using the cache?</div>
<div><br></div><div>I use the following:</div><div><div>set(CPACK_INSTALL_CMAKE_PROJECTS)</div><div>foreach(component ${INSTALL_BUNDLES})</div><div> list(APPEND CPACK_INSTALL_CMAKE_PROJECTS "@PROJECT_BINARY_DIR@;Apache Celix;${component};/")</div>
<div>endforeach(component)</div><div>list(APPEND CPACK_INSTALL_CMAKE_PROJECTS "@PROJECT_BINARY_DIR@;Apache Celix;framework;/")</div><div><br></div><div>CONFIGURE_FILE(${PROJECT_SOURCE_DIR}/cmake/templates/CPackConfig-Installation.in CPackConfig-Installation.cmake @ONLY)</div>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Hope that gives you some ideas to start from,<br></blockquote><div><br></div><div>Yes it dit, it also gave me the idea that my solution is in the right direction and that CMake/CPack doesn't support groups in its configuration. Thanks!</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
regards Mark<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Met vriendelijke groet,<br><br>Alexander Broekhuis
</div></div>