On Tue, Aug 07, 2007 at 07:45:07PM +0200, Eric Noulard wrote: > 2007/8/7, Frederik Deweerdt <[EMAIL PROTECTED]>: > > On Mon, Aug 06, 2007 at 06:31:32PM +0200, Eric Noulard wrote: > > > 2007/8/6, Alexander Neundorf <[EMAIL PROTECTED]>: > > > 2) Those files MUST define the following variables > > > > > > CPACK_GENERATOR_NAME --> the name of the GENERATOR > > > e.g. SET(CPACK_GENERATOR_NAME "RPM") > > > > > > CPACK_RPM_OK will be set after INCLUDing(CPackRPMGenerator.cmake) > > > such that cpack will know if the generator may be used on the current > > > platform or not. > > > > > > then afterwards > > > CPACK_RPM_TYPE --> the type which may be source, binary, both > > > e.g. SET(CPACK_RPM_TYPE "binary") > > > whereas > > > SET(CPACK_SRPM_TYPE "source") > > > and > > > SET(CPACK_ZIP_TYPE "both") > > > or may be > > > SET(CPACK_ZIP_TYPE "binary;source") > > > > > Hi Eric, > > > > How to specify which files go to the -devel RPM and the ones that go to > > the plain binary RPM? > > You are right, my proposal does not take this into account. > > But I'm afraid this is an issue I did not think about for now. > My CURRENT point of view is that CPack may generate > two "simple" kind of package > > - binary which basically packages the result of a "make install" > - source which basically packages the source tree > > I think your question is how to generates several packages from a > single CMake handled project. > My answer is that this "sub-package" splitting should be handled > through the CMake INSTALL "component" feature. > Thanks, didn't think of it. This could be also achieved using conditionals on CMAKE_BUILD_TYPE, I think. BTW, I also couldn't figure out how to use the "component" stuff, anybody?
Regards, Frederik _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake