Every time I create a superbuild using ExternalProject_Add sooner or
later a project will not support cmake, but will have buried within its
bowels a visual studio solution project .sln and sometimes gobs of
.vcxproj files (read CPython). Now ofcourse include_external_msproject
can do this.
Also at
https://cmake.org/cmake/help/latest/module/CMakePackageConfigHelpers.html?highlight=configure_package_config_file
set(INCLUDE_INSTALL_DIR include/ ... CACHE )
set(LIB_INSTALL_DIR lib/ ... CACHE )
set(SYSCONFIG_INSTALL_DIR etc/foo/ ... CACHE )
#...
include(CMakePackageConfi
@Robert
So how do I go about using it in 3.9? And more importantly does it
work? Does it generate hybrid CPP/CU projects that can be compiled in
visual studio the way FindCUDA (did/does?).
Currently using FindCUDA, but I have had some CUDA 7.5 / 8.0 and VS
13/15 cats in a bag trouble. Fi
@Caleb
I am asking how do I get it to work in post 3.8 or 3.9. Does it work.
I know how it worked before CMake 3.2 and prior both on Linux and
windows... ie ... it did not without considerable manual futzing due to
NVIDIA's inability to put their goop in a standard location that they
would
@Robert
>> It works and will generate hybrid C++ and CUDA projects. A very
simple example of making a library and an executable that uses both
languages can be seen at:
https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0/Tests/Cuda/ConsumeCompileFeatures/CMakeLists.txt
Thanks for the example
@Robert
Adding CUDA to my PROJECT(4DRTProto CXX CUDA)
Yields:
CMake Error at
C:/projects/4DRTProto/4DRTProto_3rdParty/platform/tools/cmake-3.9.0-rc6-win64-x64/share/cmake-3.9/Modules/CMakeTestCUDACompiler.cmake:45
(message):
The CUDA compiler "C:/Program Files/NVIDIA GPU Computing
Tool
Saying I could get this to work, which it is not how, would one using
project:
Project( myproject CXX CUDA)
specify the version of CUDA to use if I have CUDA 7.5 and 8 installed
simultaneously. FindCUDA could do it. And say if version of cuda could
be specified why not c++ 0x or 11... Ya
@Robert
I created a fresh simple cmake project in 3.9. This appeared to find
CUDA 8.0 successfully so it may have something do with my other project
settings that I am trying to get to work with 3.9, VS13, CUDA 7.5/8.0.
Using:
message( CUDACXX = ${CUDACXX})
message( CMAKE_CUDA_COMPILER = ${
With simple stand alone cmake 3.9 project using
cmake_minimum_required(VERSION 3.9)
project(cmake_testing CXX CUDA)
I can get a simple app to compile. It however fails to run with:
GPU Device 0: "GeForce GTX 960M" with compute capability 5.0
Current device is [0]
Current device is [0]
CUDA e
Things I have tried:
Install Visual Studio 15
Install CUDA 8.0 + patch
Install Visual Studio 13 <- Yes Nvidia / CMake'ers sometimes we have to
do back ports
Install CUDA 7.5
VS 13 will run CUDA 8.0 samples nbody/deviceQuery
VS 13 does not run CUDA 7.5 samples nbody or any example attempting t
Saga novella continues:
>> Next I am going to remove all NVIDA drivers and try reinstall of
CUDA 7.5 see if I can get deviceQuery to report 7.5/7.5.
Nvidia 352.65 driver removal from Add/Remove Programs
Device Manager -> NVIDIA GeForce GTX 960M -> General reports "device has
been disabled"
Could this be a Win 10 Pro/Enterprise CMake combo issue. I brought over
demo project to OS refreshed M4700. Was Win7 Pro now Windows 10
Enterprise.
Dell M4700 combo is:
Device 0: "Quadro K1000M"
CUDA Driver Version / Runtime Version 8.0 / 7.5
CMake 3.2 or 3.9 will build but not
My responses are inline.
As are mine.
On Sat, Jul 29, 2017 at 7:00 PM, Brian J. Davis http://public.kitware.com/mailman/listinfo/cmake>> wrote:
>/@Robert />//>/I created a fresh simple cmake project in 3.9. This appeared to find
CUDA />/8.0 successfully so it may have so
Since I do not see a FindNmake or the likes, is there a way to call
Nmake from a CMakeLists.txt file?
The root CMakeList.txt file contains:
set( LIBTIFF_CONFIGURE_FILE ${TOP}/CMake/libtiff/CMakeLists.txt.config )
configure_file( ${LIBTIFF_CONFIGURE_FILE}
${SOURCE_DIR}/libtiff/CMakeLists.txt.
14 matches
Mail list logo