[CMake] Package: dev vs runtime package

Mathieu Malaterre mathieu.malaterre at gmail.com
Fri Jun 6 16:58:14 EDT 2008


Hi David,

  After a google search I actually found your previous post too:

http://www.cmake.org/pipermail/cmake/2008-January/019327.html

Thanks, will look into paraview's code for example.

Thanks
-Mathieu


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



-- 
Mathieu


More information about the CMake mailing list