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...
One remark about CPACK_MONOLITHIC_INSTALL, it seems to be taken into at CMake time and not at CPack time? i.e. cpack -D CPACK_MONOLITHIC_INSTALL=1 NSIS does not work whereas cmake -DCPACK_MONOLITHIC_INSTALL=1 + cpack NSIS is OK. is it supposed to work at CMake time only ? if this is the case my initial idea was to be able to chose at CPack time. -- 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
