Currently we don't provide the compiler id and version for the CUDA
host compiler.
If you are interested in having this information can you please create
an issue on the cmake gitlab: https://gitlab.kitware.com/cmake/cmake
On Fri, May 10, 2019 at 12:09 PM JR Cary wrote:
>
> Thanks, Chuck.
>
> I
We have had luck packaging all the CTestTestFile.cmake files, and using sed to
adjust paths for the target location. You need to install ctest on the test
machine, along with all the tests.
The only paths we change are the test output location (ie google test .xml
files: this might not apply t
On Fri, 2019-05-10 at 12:06 -0500, Dustyn Blasig wrote:
> Hi All,
>
> I'm curious if anyone has had success allowing two testing paths to
> coexist well.
>
> Currently, we are using CTest to run our test executables with `make
> test`. However, on our Jenkins system, the build machines have the
>
Hi All,
I'm curious if anyone has had success allowing two testing paths to coexist
well.
Currently, we are using CTest to run our test executables with `make test`.
However, on our Jenkins system, the build machines have the whole
development stack but the test machines do not. So we need a way
Thanks, Chuck.
I was not clear on my question, which is: When I specify the two
compilers, how
do I get, e.g., CMAKE_CUDA_HOST_COMPILER_ID and
CMAKE_CUDA_HOST_COMPILER_VERSION?
I need these to determine consistency between the CUDA version and the
host compiler
version, so that I can disab
Hi John,
Two different compilers in the same project for the same language is messy,
but in your case it's directly supproted as a special case for cuda using
the CMAKE_CUDA_HOST_COMPILER CMake variable or the CUDAHOSTCXX environment
variable.
--
Chuck Atkins
Staff R&D Engineer, Scientific
