2010/8/3 Eric Noulard <eric.noul...@gmail.com>: > 2010/8/3 David Cole <david.c...@kitware.com>: >> On Mon, Aug 2, 2010 at 6:57 PM, Eric Noulard <eric.noul...@gmail.com> wrote: > >>> >>> 2. may always be an option because it was the behavior we had before the >>> component support and ALL CPack generator may handle an all-in-one >>> package. >>> We could add an OPTION like CPACK_COMPONENT_ALL_IN_ONE which >>> would basically tell CPack to ignore the component aspect. >> >> FYI: there already is an option that's similar to this, I >> think: CPACK_MONOLITHIC_INSTALL >> Does that have the effect you're talking about or are you thinking something >> different? > > You are right that's the idea. > I wasn't aware of that option... I'll go for a thorough read of > CPack.cmake documentation > before re-inventing existing options...
After a remark made by Clint and some thought. CPACK_MONOLITHIC_INSTALL is not covering the whole need and I think we need a CPACK_COMPONENTS_ALL_GROUPS_IN_ONE_PACKAGE options. Have a look at the updated bug entry and the description of all cases: http://public.kitware.com/Bug/view.php?id=10736 There is a fifth patch to the current patchset to propose that. Clint would you be able to give it a try and tell us if with this last patch (still cumulative) your needs are covered? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org _______________________________________________ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers