Re: [CMake] Beginning to compiling CMake file

Hi, From my understanding I must compile with Powershell ? These variables mentioned in the appveyor file they are environment variables which are set within cPanel ? What is the first step I need to do and with what file from the repository whether in PowerShell or CMake or both ? Thanks

Re: [CMake] VS 2017 + CUDA 9.0

The CUDA_ADD_LIBRARY infrastructure is deprecated and it is understandable that it isn't aware of the toolsets since it is based on custom commands. I recommend using the new CUDA first class language support. You can find an intro blog post on using this at: https://devblogs.nvidia.com/building-c

Re: [CMake] VS 2017 + CUDA 9.0

Hi Robert, thanks for the hint - indeed, it somewhat solved the problems I have mentioned. However, the CMake backend for CUDA (one of the preprocessing steps in CUDA_ADD_LIBRARY for example) calls nvcc -M (do get dependencies), and this command first tries to load vcvars.bat without any comman

Re: [CMake] Fwd: Boost + CMake + Windows + Sanity -> Possible?

On 08/08/18 12:39, Chris Wilson wrote: Having set BOOST_ROOT, FindBoost should just work. In this case, I didn't need to compile any of Boost, only its headers, but if you do need to, then you can change its CONFIGURE_COMMAND and BUILD_COMMAND. Portable build and configure commands can be fo

[CMake] Fwd: Boost + CMake + Windows + Sanity -> Possible?

Hi all, I solved this problem (or a very similar one) by using a CMake superbuild which builds Boost and then my project, like this: # Version of Boost to download, unpack, and compile Box Backup agai

Re: [CMake] Can't find boost libs on VS2017 CMake 3.12

Update: I put this before find packages boost and now it WORKS: if (WIN32)   set (Boost_USE_STATIC_LIBS ON) endif (WIN32) Think I tried this earlier with no luck but it may have been obscured by cache or some other attempts. On 03-08-2018 13:24, Søren wrote: Thanks Debug output shows * that

Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?

Hi Mateusz, I absolutely agree - use the latest CMake! That will help fix and bugs and ensure it works with more up-to-date versions of Boost. My cut and paste instructions were from 2 different computers, and the one I wrote the mail on has an older version of CMake - I wasn't suggesting peopl