Re: [CMake] specifying path for license file for commercial compiler?

I agree that a toolchain file is more appropriate, noting that typically modifying the environment variables is much more common for there's compilers (particularly using environment modules). However, since you've started clearly you would rather not set the environment variables, there may be an

Re: [CMake] specifying path for license file for commercial compiler?

May be using a toolchain file is more appropriate. See https://cmake.org/cmake/help/v3.12/manual/cmake-toolchains.7.html Le ven. 6 juil. 2018 à 22:59, Clune, Thomas L. (GSFC-6101) < thomas.l.cl...@nasa.gov> a écrit : > To use the Intel compiler, one must use an environment variable that > specif

[CMake] specifying path for license file for commercial compiler?

To use the Intel compiler, one must use an environment variable that specifies the path to the license file. E.g., export INTEL_LICENSE_FILE=/usr/local/intel/license Other commercial compilers use a very similar mechanism.I had hoped to capture such information in a cache file so that

Re: [CMake] Using CMake to link C++ and CUDA Object file

To be clear the FindCUDA module currently does two things it finds the location of the CUDA SDK and it also adds the 'cuda_' commands. In your case you might still need to use FindCUDA to find the location of the thrust include directory, or you can find the location yourself by using find_path li

Re: [CMake] Using CMake to link C++ and CUDA Object file

Thanks for your response, Robert. If I don't use find_package(CUDA), I run into the following problem: fatal error: thrust/host_vector.h: No such file or directory I guess this is needed if I am using Thrust/CUDA? Thanks, Quang On Fri, 6 Jul 2018 at 06:38, Robert Maynard wrote: > if you are

Re: [CMake] Using CMake to link C++ and CUDA Object file

if you are using the new first class cuda language, as seen by `project(MyTest LANGUAGES CXX CUDA)` you shouldn't use the old find cuda package or the associated cuda_add_library calls. When using the first class cuda language simply use add_library. The other difference I notice is that you makef

Re: [CMake] CMAKE_ARGS for FetchContent

On Fri, Jul 6, 2018 at 9:49 PM, Mads Andreasen wrote: > Hi Craig > > Thanks for getting back to me. > I was hoping to be able to build the library with fetch content, so that > the FindXXX would automatically work. > If you want to use FindXXX, you need to use ExternalProject and a superbuild st

Re: [CMake] CMAKE_ARGS for FetchContent

Hi Craig Thanks for getting back to me. I was hoping to be able to build the library with fetch content, so that the FindXXX would automatically work. If I use your proposed approach: if(NOT jsoncpp_POPULATED) FetchContent_Populate(jsoncpp) add_subdirectory(${jsoncpp_SOURCE_DIR} ${jsoncpp_

Re: [CMake] CMAKE_ARGS for FetchContent

On Fri, Jul 6, 2018 at 8:25 PM, Mads Andreasen wrote: > Hi, > > I am trying to work with FetchContent in cmake 3.11. > I want to use the jsoncpp library and use FetchContent to get and build it. > FetchContent can only download it. You need to build it as a separate step (you should avoid buildi

[CMake] CMAKE_ARGS for FetchContent

Hi, I am trying to work with FetchContent in cmake 3.11. I want to use the jsoncpp library and use FetchContent to get and build it. I also want to configure the jsoncpp build with some cmake arguments and I can't seem to get that right. My CMakeLists.txt looks like this: ***

[CMake] Equivalent of fixup_bundle for frameworks?

Hi All, Before I set of on lots of custom functionality is there an equivalent to fixup_bundle for frameworks for iOS/macOS? The task is roughly the same, gather the required dylibs, copy them to the frameworks (in the case of iOS) folder, adjust rpaths…. Thanks in advance! Kind Regards, Jame