Hi Mattias, I've just successfully done some tests. The only problem I came across was that make package_source sat there forever till I killed it. I build the OSG in source so perhaps this is the cause of the problem with it. The other packaging targets worked fine. I'll try an out of source build and see if that fixes things.
Since enough is working to get others to test I've checked things in. In terms of zip vs bzp2 vs gz, I'm inclined to suggest that we only do one, or perhaps stick to .zip for Windows, and gz for everything else. I also wonder about the platform naming of packages, we might need to add the architecture as well to distinguish between 32bit vs 64bit, or VS8 vs VS9. Robert. On Fri, Dec 12, 2008 at 10:53 AM, Mattias Helsing <[email protected]> wrote: > cpack and ctest were initially shipped with cmake 2.6.0 so yes - I > should have put guards aournd the BUILD_PACKAGE option. I have testd > the submission with cmake-2.6.2 on WinXP and Linux(ubuntu intrepid). > If you decide to commit eventually I willl test on 2.6.0 (and put > proper guards) on further devel submissions of these parts. > > >From what I can see (cmake list, debian list and other sources) cpack > is still moving (like cmake) so regarding cpack functinoality we may > need to keep up. > > cheers > Mattias > >> >> Robert. >> >> On Thu, Dec 11, 2008 at 6:58 PM, Mattias Helsing <[email protected]> >> wrote: >>> Hi all, >>> >>> I have developed the earlier cpack example a bit. Perhaps you could >>> consider these initial cpack support scripts. It is hidden behind a >>> BUILD_PACKAGES option so won't affect the normal user. The submission >>> 1) set the COMPONENT attribute on all cmake install commands. >>> COMPONENT names are according to >>> http://www.openscenegraph.org/projects/osg/wiki/Community/Packaging >>> >>> 2) provide cmake script and a template for creating CPack >>> configuration files. It will generate target for creating packages >>> with everything that gets "installed" (make package on unx, project >>> PACKAGE in MSVC) plus targets for generating one package per COMPONENT >>> (i.e. libopenscenegraph-core etc.). >>> >>> I have temporariliy uploaded some examples to >>> http://www.openscenegraph.org/projects/osg/wiki/Community/People/MattiasHelsing >>> >>> If this submission makes it into svn we can develop it to generate >>> rpms, installers for windows and mac (I know at least J-S don't like >>> these but there may be others who do ;) and even DEBs (not sure if we >>> can make them "ubuntu-ready" but they eventually may - at least we >>> could put a deb on the website) >>> >>> Feedback more then welcome of course >>> cheers >>> Mattias >>> >>> _______________________________________________ >>> osg-submissions mailing list >>> [email protected] >>> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org >>> >>> >> _______________________________________________ >> osg-submissions mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org >> > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
