Hi Robert, all On Wed, Dec 3, 2008 at 1:19 PM, Robert Osfield <[EMAIL PROTECTED]> wrote: > Hi Matthias, > > I was unware of CPack. It certainly sounds like something that might > take us further along the road to standardising/automating more of > this work. > > It would be great if you produce an example. > > Robert. >
Here is a simple cpack showcase. Basically i have added COMPONENT directives to all calls to cmake's install command. I then use these components to generate cpack configuration files. I have modified the SETUP_PLUGIN macro to be aware of an extra parameter. This I use for distinguishing plugins that shold be in separate package (not core). In this showcase i have only implemented this for the gdal plugin. I think this example shows that the impact on our existing cmake scripts is small. We can then develop cmake macros to produce almost any packages we want. These macros would then be hidden for the regular user of course(like OSG_MAINTAINER) These files work on my ubuntu intrepid laptop with cmake.2.6.2. There are differences regarding cpack functionality between patch0 and patch2 but haven't tested whether these files work with cmake-2.6.0 nor have I tested them on windows yet. Windows would require the 7-zip program and make use of the ZIP generator Here is how I use them first unpack tar file in OpenScenGraph source root cd <osg_build_dir> cmake <osg_src_dir> cpack --config CPackConfig-libopenscenegraph-core.cmake -G TGZ the -G switch instructs cpack to generate tar.gz file. Other options are STGZ, RPM, DEB(won't work but u can try) and some others. CPackConfig-libopenscenegraph-core.cmake have siblings also generated in the build directory. oh there's lots to say about what we could do but I will stop here and await your opinions cheers Mattias
cpack_sample.tar.gz
Description: GNU Zip compressed data
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
