[CMake] [nitpick] Incorrect FILE(COPY) error message

Hello, The FILE(COPY) command displays an incorrect error message when its argyument is empty: $ cat >x.cmake FILE(COPY "" DESTINATION ".") $ cmake -P x.cmake CMake Error at x.cmake:1 (FILE): file INSTALL encountered an empty string input file name. INSTALL should obviously be COPY. This happ

[CMake] how to map configurations from include_external_msproject() ?

I'm trying to include legacy Visual Studio projects into a cmake generated solution like this: project(Crypto) include_external_msproject(${PROJECT_NAME}_vcproj "${CMAKE_CURRENT_SOURCE_DIR}/${PROJECT_NAME}_vs90.vcproj" ) # add_dependencies(${PROJECT_NAME}_vcproj # ) add_library(${PROJECT_NAM

Re: [CMake] how to map configurations from include_external_msproject() ?

Hi, Am 9. Februar 2016 13:36:03 MEZ, schrieb Gerhard Pobinger : >I'm trying to include legacy Visual Studio projects into a cmake >generated >solution like this: > >project(Crypto) > >include_external_msproject(${PROJECT_NAME}_vcproj > "${CMAKE_CURRENT_SOURCE_DIR}/${PROJECT_NAME}_vs90.vcproj" >

Re: [CMake] CMAKE_MODULE_PATH ignored

Hi, I myself use statements like: list( INSERT CMAKE_MODULE_PATH 0 ${CMAKE_SOURCE_DIR}/modules ) at the beginning of my main CMakeLists.txt file, and it works exactly as one would expect. I also override some CMake provided modules like this. Cheers, Attila > On 08 Feb 2016, at 20:22,

[CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi, I'm a long time user of CMake (and huge fan of it) but newly registered on this list, so please forgive me if I have missed something regarding the new 3.5 series. I use CMake with the GCC ARM Embedded compiler ( https://launchpad.net/gcc-arm-embedded) to cross-compile my project (Windows hos

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi Thibault, Can you post your toolchain file? - Chuck On Tue, Feb 9, 2016 at 9:10 AM, Thibault Genessay wrote: > Hi, > > I'm a long time user of CMake (and huge fan of it) but newly registered on > this list, so please forgive me if I have missed something regarding the > new 3.5 series. > >

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi Thibault, Thanks for trying the release candidate! On 02/09/2016 09:10 AM, Thibault Genessay wrote: > I installed 3.5 and the build broke While CMakeForceCompiler is deprecated we think it should still work in most cases where it worked before, just with a warning. What actually breaks? > C

[CMake] ifort: command line remark #10148: option 'i_dynamic' not supported

Hi, I am using cmake 2.8.12.2, and I'm getting this warning when I attempt to link a fortran program or library. ifort: command line remark #10148: option 'i_dynamic' not supported I cannot find very much about this error searching the web. What does this mean? Thanks -- Powered by www.kitwa

[CMake] Precedence of SYSTEM and non-SYSTEM include directories

I ran into a problem recently where a project I was building set a SYSTEM include directory which was already a non-SYSTEM include directory imported from a dependency. When this happened, CMake dropped the non-SYSTEM directory in favor of the SYSTEM one, causing my build to fail. Should this be t