[CMake] CPack: How to add the Build Configuration Type to the created installer

2009-11-05 Thread Michael Jackson
I would like to generate installers for both a Release and a Debug build but have them be separate installers under Visual Studio. Currently when I build the PACKAGE project in my solution I get a nice installer with a name like: AIMRepresentation-2009.11.03-win64.exe which is generally

Re: [CMake] CPack: How to add the Build Configuration Type to the created installer

2009-11-05 Thread Eric Noulard
2009/11/5 Michael Jackson mike.jack...@bluequartz.net: I would like to generate installers for both a Release and a Debug build but have them be separate installers under Visual Studio. Currently when I build the PACKAGE project in my solution I get a nice installer with a name like:

Re: [CMake] infinite loop when trying to change the compiler in CMakeLists.txt

2009-11-05 Thread Eric Noulard
2009/11/5 btho...@nexus.hu: Dear All, I am managing a CFD code where wish to set the CMAKE_C_COMPILER and CMAKE_CXX_COMPILER to openmpi wrappers. So far i was using cmake 2.4.7 and in the CMakeLists.txt the following lines were working perfectly: SET(CMAKE_C_COMPILER

Re: [CMake] CPack: How to add the Build Configuration Type to thecreated installer

2009-11-05 Thread Dixon, Shane
# Cpack section SET(CPACK_PACKAGE_FILE_NAME ${PROJECT_NAME}-${VERSION}-win32-${CMAKE_BUILD_TYPE}) If you don't want the -release to show up on the release version, you could put an if statement above this that checks the build type and creates a variable (I call mine PACKAGE_POSTFIX) and you

Re: [CMake] infinite loop when trying to change the compiler in CMakeLists.txt

2009-11-05 Thread Marcel Loose
Another way to deal with this is to set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER *before* the first project() command. You could do this in the main CMakeLists.txt file or in a separate CMake script file that you include before the project() command. In fact, this is what also happens when you do