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 c
# 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
2009/11/5 :
> 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 ${MPI_INSTALL_ROOT}/bin/mp
2009/11/5 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.0
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 f
I think the best way to do that is with an initial cache via the -C flag
to cmake. Then you can set the initial CMAKE__COMPILER option in
a CMake file and start with that file.
I currently don't do this, but I should. At the moment I am doing this
wrong by using the CMAKE_TOOLCHAIN_FILE vari
