Hi On Tue, Mar 6, 2012 at 2:27 PM, Eric Noulard <[email protected]> wrote:
> It is even necessary for more than "just testing" because the > CPackConfig.cmake file may be > overwritten by CPack next time you change your CMakeLists.txt. > > CPackConfig.cmake is "generated" by the > include(CPack) > in your CMakeLists.txt. > > Ultimately it may be useful to "configure_file" your > CPackProjectConfig.cmake.[in] > and put some generated logic in it depending on any CMake variable. > So the next step would be to configure e.g. CPACK_CROSSPACKAGING and CPACK_WIN32 in my project config file and try to make GetPrerequisites work with them? If you manage to do that kind of cross-packaging it could be worth a > page on the Wiki. > Sure, can add it when's its time to ;) Best regards, Dominik
-- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
