With CUDA_SEPARABLE_COMPILATION enabled, I'm always getting linking
errors when I try to build. Seems it's looking for a directory that
doesn't exist:
'/build/CMakeFiles/SlicerLib.dir/Debug
If I manually create this directory, everything works. Seems that
either the directory path isn't being co
Ah, thanks!
On Fri, Apr 17, 2015 at 3:36 PM, James Bigler wrote:
> FindCUDA doesn't look for a specific version, but rather checks to see if
> the version it found is the one you asked for. You can set the
> CUDA_TOOLKIT_ROOT_DIR to the one you want (and reconfigure - I've set it up
> to easily
FindCUDA doesn't look for a specific version, but rather checks to see if
the version it found is the one you asked for. You can set the
CUDA_TOOLKIT_ROOT_DIR to the one you want (and reconfigure - I've set it up
to easily change this), or you can change your environment in Windows to
point to the
Well, if the file needs to have the substitutions performed, like after an
edit, CMake will have to run. What you could do is write a standalone cmake
script that just does the configure file step, then add it as a custom
command on a custom target, just running that configure script in script
mode
I'm working within a very large project on a python script. The script
gets passed through configure_file to replace some @VAR@ strings with some
file paths that are defined when cmake is run; this generates the final
script. The side effect is that whenever I modify the file and run make,
it re-
Hi,
I'm trying to use Cmake 3.2.2 to build with Cuda7 on Windows 8. I have
both Cuda 6.5 and Cuda 7.0 installed in these locations:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v6.5
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v7.0
When I try these:
find_package(CUDA "7.0" REQUIRED)
On 4/17/2015 8:44 AM, Jon Hodgson wrote:
> The CXX compiler identification is AppleClang 5.1.0.5030040
> The C compiler identification is AppleClang 5.1.0.5030040
Good.
> But then it bombs out at the line
>
> PROJECT(${PROJECT_NAME} CXX C)
>
> with the error
>
> No CMAKE_CXX_COMPILER could be
Hi Jon,
I can't really explain why, but I've seen the same problem on a colleague's Mac
as well. On my machine, it works just fine, but to get it working across all of
our Macs, I find I need to explicitly define the compilers by passing these
arguments to CMake on the command line:
-DCMAKE_C_
HI,
Running OSX Snow Leopard, XCode 5.1.1
Command line tools installed.
If I type
clang --version
at the command line I get version 5.1
CMake 3.2.2
The first lines of outpuit I get are
The CXX compiler identification is AppleClang 5.1.0.5030040
The C compiler identification is AppleClang 5.1
On 17.04.2015 13:09, Sylvain Doremus wrote:
I have a strange output, related to the minimal CMakeLists.txt that I've
provided with this email.
My CMake version is 3.2.1, on Windows Seven SP1, the tested generators are
Visual Studio 10 2010 and Visual Studio 10 2010 Win64.
Here is the output I'
Eliminate your DOWNLOAD_COMMAND. CMake knows how to do it with just
the URL_MD5, DOWNLOAD_DIR and SOURCE_DIR information
HTH,
David
On Fri, Apr 17, 2015 at 1:32 AM, Cedric Doucet wrote:
>
> Hello David,
>
> thank you very much for your help.
>
> Unfortunately I may do something wrong becaus
I have a strange output, related to the minimal CMakeLists.txt that I've
provided with this email.
My CMake version is 3.2.1, on Windows Seven SP1, the tested generators are
Visual Studio 10 2010 and Visual Studio 10 2010 Win64.
Here is the output I've got:
TestFolder/type
TestFolder
TestFolde
Hi Daniel.
Your generator expression contains a space (between "," and "-I"). Is it
quoted? Generator expressions are just normal strings until generate time,
and space normally separates CMake arguments. In other words, like this:
target_compile_options(trgt
-I$, -I>)
the command has *two* argu
13 matches
Mail list logo