Look at the cmake_install.cmake file in the top level of your build tree.<br><br>There should be references to CMAKE_INSTALL_COMPONENT and COMPONENT variables.<br><br>make install will typically do a "cmake -P cmake_install.cmake" -- to do a COMPONENT based install, you can do:<br>
<br>cmake -DCOMPONENT=Runtime -P cmake_install.cmake<br><br><br>HTH,<br>David<br><br><br><div class="gmail_quote">On Fri, Jun 6, 2008 at 2:04 PM, Mathieu Malaterre <<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thu, Jun 5, 2008 at 4:02 PM, Mathieu Malaterre<br>
<<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>> wrote:<br>
> On Thu, Jun 5, 2008 at 3:54 PM, Timenkov Yuri <<a href="mailto:ytimenkov@parallels.com">ytimenkov@parallels.com</a>> wrote:<br>
>> On Thursday 05 June 2008 17:47:27 Mathieu Malaterre wrote:<br>
>>> On Thu, Jun 5, 2008 at 3:39 PM, Timenkov Yuri <<a href="mailto:ytimenkov@parallels.com">ytimenkov@parallels.com</a>> wrote:<br>
>>> > On Thursday 05 June 2008 17:36:06 Mathieu Malaterre wrote:<br>
>>> >> Hi,<br>
>>> >><br>
>>> >> Has anyone started working on the development vs runtime package.<br>
>>> >> For example the runtime package should only install libfoo.so.1.2<br>
>>> >> while the -dev package would distribute the libfoo.so symlink to<br>
>>> >> libfoo.so.1.2.<br>
>>> >> I know that cpack does not support multiple package right now, but I<br>
>>> >> would like at least be able to generate the runtime package (discard<br>
>>> >> the .so symlink from the package).<br>
>>> >><br>
>>> >> Thanks for suggestion,<br>
>>> > I've filed similar request to tracker (<a href="http://public.kitware.com/Bug/view.php?id=6850" target="_blank">http://public.kitware.com/Bug/view.php?id=6850</a>)<br>
>>> > And it was solved in CMake-2.6.<br>
>>> ><br>
>>><br>
>>> Very nice !<br>
>>><br>
>>> I simply need to make NAMELINK_ONLY /NAMELINK_SKIP configurable (using<br>
>>> a cmake var) and using two build tree, generate my two packages.<br>
>> Nope, making 2 build trees is overkill :)<br>
>> I suppose You need 2 components instead (I didn't tested this solution, but I suppose it should work):<br>
>><br>
>> install(TARGETS mylib DESTINATION lib COMPONENT runtime NAMELINK_SKIP)<br>
>> install(TARGETS mylib DESTINATION lib COMPONENT devel NAMELINK_ONLY)<br>
><br>
<br>
</div>I am trying right now, but I cannot figure out how to pass the option<br>
to cpack so that it runs on either the 'runtime' or the 'devel'<br>
component type.<br>
<br>
Anyone ?<br>
<br>
thanks<br>
<div><div></div><div class="Wj3C7c">--<br>
Mathieu<br>
_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>