On Sunday 22 August 2010, Eric Noulard wrote: ... > CPack is not aware **AT ALL** of subprojects :-( > > It's even worse, since CPack is not meant to be included more than once > in the same tree. > In fact you already know that because you are the reporter of this: > http://public.kitware.com/Bug/view.php?id=10751 > > A related discussion on the ML: > http://www.cmake.org/pipermail/cmake/2010-August/038648.html > > So I would say, unless I misunderstood something, > that **currently** you CAN NOT use "subproject" to do any grouping with > CPack. If any subproject do include(CPack) while your toplevel project does > it as well, you'll get unexpected behavior. > The most probable consequence is that is you call "make package" in the > toplevel project you'll get a source package instead of a binary package > :-) > > What you CAN ALREADY do is to use your toplevel project to build a package > which contains all subprojects. You can even use component in the > subproject(s) it will > work as expected. > > If we want to be able to include(CPack) several times, many thing > should be changed
This would probably make cpack usable for KDE, where we have a lot of apps (subprojects) inside one svn tree :-) > and we should specify the expected behavior very precisely, I do not > think it's as easy > as it may seems. Definitely on my workplan now :-( Cool, thanks for your efforts :-) Alex _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
