Hi Doug
Ok. Works now I've upgraded to version 2.8.8 from 2.8.0.
I was reaching the conclusion that components were more suited to
installers such NSIS - but with a lot of confusion.
Your latest example is elegant simplicity - it should go on the wiki.
Thanks so much for clearing things up.
I've update my example code here to do this; it results in much easier
to configure individual packages than trying to force the components
(never designed for independent packages from one project), and is
extendable to support other generators that do not support components.
https://github.com/s
Ok - not what I get on ubuntu LTS 10.4. Perhaps I need the latest version?
( I ran the original files with just the missing line (?)
"install(CPack)" added).
$ cmake -version
cmake version 2.8.0
$ ls
$ cmake ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
--
Woops; didn't mean to respond off list.
Anyway, basically my suggestion is as part of your build generate a folder like:
${CMAKE_CURRENT_BINARY_DIR}/deploy-package-XXX/
And copy all the file you want to deploy as part of your package into
that directory.
Then generate a CMakeLists.txt file with
I've been through this and experimented with samples kindly provided by
another user. Nothing works for debian packaging. What I think will work
is a "workaround" from another user in 2008
_http://www.cmake.org/pipermail/cmake/2008-April/020967.html_, where I
generate my own CPackConfig-runti
2012/8/8 m.hergarden
> I have found this to work for RPM files:
>
> You have to define components using:
> cpack_add_component(runtime DISPLAY_NAME runtime REQUIRED INSTALL_TYPES
> all)
>
You are right defining components is the easiest way to produce several
packages (deb, rpm, zip, etc...)
Th
I have found this to work for RPM
files:
You have to define components using:
cpack_add_component(runtime DISPLAY_NAME runtime REQUIRED
INSTALL_TYPES all)
For rpm I had to set this:
SET(CPACK_RPM_COMPONENT_INSTALL "ON"
(Greppi
Hi
Got my shiny new cmake build system going for my project on windows, Ubuntu,
and Mac.
Despite a fair bit of research I'm still not sure how to generate 2 separate
debian packages from the same cmake files - say myapp.deb and myapp-dev.deb.
I think what I want is somehow for it to write out