[CMake] cuda_wrap_srcs error

2017-12-15 Thread Ajay Panyala
Hello, I am trying to compile a simple cuda program to an object file with "cuda_wrap_srcs" using the following CMakeLists.txt: cmake_minimum_required(VERSION 3.7 FATAL_ERROR) > project (TEST C CXX) > include(FindCUDA) > cuda_wrap_srcs(hello OBJ hello_test hello-world.cu OPTIONS -O3) *I see the

Re: [CMake] Using SET_TARGET_PROPERTIES and IMPORTED_LINK_INTERFACE_LIBRARIES

2017-12-15 Thread Saad Khattak
Thank you Marc. I found that the following also works: target_link_libraries(LibD INTERFACE LibA LibB) However, my guess is that in the future the above may break as it is assuming LibD is an INTERFACE instead of an IMPORTED library. I'll switch to your version instead as it seems to be more corr

Re: [CMake] Using SET_TARGET_PROPERTIES and IMPORTED_LINK_INTERFACE_LIBRARIES

2017-12-15 Thread Craig Scott
On Thu, Dec 14, 2017 at 7:40 PM, CHEVRIER, Marc wrote: > I think you can fill a bug about erroneous behaviour when a list is > specified with command set_target_properties for property > IMPORTED_LINK_INTERFACE_LIBRARIES. > You can set multiple properties with set_target_properties() and you are

[CMake] Installing and exporting multiple configurations of the same library

2017-12-15 Thread Saad Khattak
Hi, I have 4 configurations (2 for Debug and 2 for Release) and I would like to install the libraries such that they are installed in the correct directories. Installing without worrying about configurations looks like this: install(TARGETS ${LIB_NAME} EXPORT ${LIB_NAME}Config

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

2017-12-15 Thread JR Cary
Thanks.  All now configures with 3.9.4. On 12/12/17 5:50 AM, Brad King wrote: > On 12/11/2017 04:34 PM, John Cary wrote: >> Bill Hoffman wrote: >>> LINK: command "xilink ... /out:FortranCInterface.exe ..." failed (exit code >>> 1169) >>> LIBCMT.lib(winapisupp.obj) : error LNK2005: >>> __crtSetUnh

[CMake] CMake and RPATH

2017-12-15 Thread Brennon Brimhall
I'm trying to install OpenCV onto an HPC system. We're trying to make sure we use RPATH, as it helps our dependency management significantly with our environment modules system. However, I've not had any success following the documentation available at https://cmake.org/Wiki/CMake_RPATH_handli

Re: [CMake] MinGW Compilers on Windows

2017-12-15 Thread J Decker
On Fri, Dec 15, 2017 at 7:39 AM, Kevan Hashemi wrote: > Dear Alan, > > Thank you for your encouragement to use the "MinGW Makefiles" generator on > Windows, and for pointing out the mingw32-make alternative to just "make" > in MSYS. > > So if you are further interested in the "MinGW Makefiles" ge

Re: [CMake] MinGW Compilers on Windows

2017-12-15 Thread Kevan Hashemi
Dear Alan, Thank you for your encouragement to use the "MinGW Makefiles" generator on Windows, and for pointing out the mingw32-make alternative to just "make" in MSYS. So if you are further interested in the "MinGW Makefiles" generator, you should remove all sh.exe versions from your PATH (i

[CMake] Building cmake with CMAKE_FIND_ROOT_PATH - binary containing dash within RPATH

2017-12-15 Thread Mike Bergmann
I try to build cmake using my own libraries. I configured using: --system-curl --system-expat --system-zlib --system-bzip2 and modified CMakeLists.txt to include: SET(CMAKE_FIND_ROOT_PATH /home/mdb/Toco/sdk/bsp/local) SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) SET(CMAKE_FIND_ROOT_PATH_MODE_LIB