Re: [CMake] Transitive linking and static libraries

On 2013-10-17 12:58, James Bigler wrote: It doesn't seem to work. I can't use target_link_libraries on an imported target. add_library(imported_lib STATIC IMPORTED GLOBAL) set_target_properties(imported_lib PROPERTIES IMPOARTED_LOCATION "${imported_lib_location}") target_link_libraries(imported

Re: [CMake] Transitive linking and static libraries

Hi James, On Thu, Oct 17, 2013 at 6:58 PM, James Bigler wrote: > It doesn't seem to work. > > I can't use target_link_libraries on an imported target. > > add_library(imported_lib STATIC IMPORTED GLOBAL) > set_target_properties(imported_lib PROPERTIES IMPOARTED_LOCATION > "${imported_lib_locatio

Re: [CMake] Transitive linking and static libraries

It doesn't seem to work. I can't use target_link_libraries on an imported target. add_library(imported_lib STATIC IMPORTED GLOBAL) set_target_properties(imported_lib PROPERTIES IMPOARTED_LOCATION "${imported_lib_location}") target_link_libraries(imported_lib other_lib) Produces an error: Attemp

Re: [CMake] Setting CPack Module Path for WiX generator

Did you try to set this up in your CMakeLists.txt? Either something like (for CMake 2.8.12): set(CPACK_WIX_TEMPLATE "${CMAKE_CURRENT_SOURCE_DIR}/mywix.template.in") Or: list(APPEND CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}") before include(CPack) should work and would expand to ful

[CMake] CMAKE_SYSTEM_NAME Returning Blank??

Hello, I am trying to set some default variables based on the platform being used. I am trying the following syntax: IF(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") # Mac OS X specific code SET(OperatingSystem "Mac OS X") message(STATUS "WORKS OK") IF(${CMAKE_SYSTEM_PROCESSOR } MATCHES

[CMake] INTERFACE_COMPILE_DEFINITIONS on imported targets

Hello all, Is there a way to set the property INTERFACE_COMPILE_DEFINITIONS in a different way for different configurations on imported targets? From the help it seem to exist COMPILE_DEFINITIONS_, but I don't see an equivalent for the "INTERFACE" version... Cheers, Daniele -- Powered by www.k

[CMake] Setting CPack Module Path for WiX generator

Hi, I am attempting to set the CPack Module Path to point to a different directory when using the WiX generator so that I may use a customized WiX.template.in configuration file. I am doing this by adding the following line into my CPackConfig.cmake file before calling cpack through the command l

Re: [CMake] Object file as first one in link.txt file

Hi. I may be wrong, but I suppose, that CMake puts linker flags BEFORE all the files to link and you use the flags to link libraries. For linking libraries you should be using the target_link_libraries CMake command. -- Gruesse, Jakub From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake

Re: [CMake] Object file as first one in link.txt file

Hi Eike, On 17 October 2013 12:32, Rolf Eike Beer wrote: > >> 1) CMake generates this link.txt (error when linking) >> /usr/bin/c++ -lfusion_io -ladios -lmxml -lmpi -lopen-rte -lopen-pal >> -lpthread -lstdc++ CMakeFiles/niio-main.dir/main.**cpp.o -o niio-main >> -rdynamic -L/home/testuser

Re: [CMake] Object file as first one in link.txt file

Am 17.10.2013 12:00, schrieb Juan Pablo Hernandez Vogt: Hello everybody, I moving a makefile to cmake, and after errors I could check that order in link chain was important. 1) CMake generates this link.txt (error when linking) /usr/bin/c++ -lfusion_io -ladios -lmxml -lmpi -lopen-rte -

[CMake] Object file as first one in link.txt file

Hello everybody, I moving a makefile to cmake, and after errors I could check that order in link chain was important. 1) CMake generates this link.txt (error when linking) /usr/bin/c++ -lfusion_io -ladios -lmxml -lmpi -lopen-rte -lopen-pal -lpthread -lstdc++ CMakeFiles/niio-main.dir/main.cp