So is the convention for hanlding auxiliary packages as follows?
Somewhere near the root of my source code tree, I create a "CMakePackages" (or similarly named) directory. Then I put all of the auxiliary packages such as DpkgDeb there. Then I modify my own CMakeLists files to specify that the "CMakePackages" directory is one of the directories searched when I issue INCLUDE(...) commands? Thanks, Christian On 7/24/07, Philip Lowman <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Convey wrote: > I need my CMake-based project to produce Debian packages in the > near-term, and RPMs probably a few months from now. Try Medhi's reworked RpmBuild and DpkgDeb macros. http://www.cmake.org/Wiki/CMakeUserUseDebian#Derived_work - -- Philip Lowman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGpd6ie0tOktX6RKkRAngGAJ49QusxxYVdTbqSDUdVFJmbnsivbwCfcNhZ +UI7rnmEtp6mpFENjCQhIRo= =6hke -----END PGP SIGNATURE-----
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
