-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CUDA 9.0 compilation issues #2814
Comments
Actually, use |
Even latest CUDA release does not seem to support 14.12 compiler, so it's not so easy to have it working with the latest VS 15.5 update... unfortunately. |
Unfortunately it will only work with VS2017 15.4 The download link is here https://docs.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 |
it's better to install older toolchain with newer vs ;) |
Actually I used v14.10 and v14.11, both failed to build for pcl and cuda with CUDA 9.0 and CUDA 9.1. How about downgrade to use v140? I ran |
We don't currently have a way to pass multiple toolsets into a build, which could explain the difference.
I want to see what we can do around this -- since we have quite a bit of control when building libraries inside vcpkg, we can likely work around any issues that occur due to the newer compiler+libraries (such as using macros to disable parts of the STL that are problematic for that particular build). |
@ras0219-msft If the modification can be temporarily done and restore automatically, then it would be great! Besides, I don't mentioned this issue for multiple toolsets in one build, but how I'm able to use vcpkg to specify the buildchain I used in the whole build process? When I look through the issues, I only found |
Adding |
I made a mistake that I thought VCPKG_PLATFORM_TOOLSET can be set in portfile. I set in triplet file and now it works! Thanks! But the issue should be open until CUDA 9 can be compiled with VS2017 |
Hi everyone, Thanks for reporting this issue! Thanks. |
I don't know whether some one has encountered any problems when using CUDA 9 with VS2017, but I actually haven't successfully built packages with cuda feature onec. Many packages which contain CUDA support haven't completely finished CUDA 9 support.
Here are messages of four major kinds of errors:
Error generating XXXXX.cu.obj
: This might occurred when the package source haven't implemented VS2017 support, since the compiler path is changed from VS2015 to VS2017.Host compiler targets unsupported OS
: MSVC compiler is (so new that) no supported by CUDA, as CUDA: Host compiler targets unsupported OS. #2791 stated.unsupported Microsoft Visual Studio version! Only the versions 2012, 2013, 2015 and 2017 are supported
: MSVC compiler is not in proper range given by CUDA. Edit<CUDA-Path>/include/crt/host_config.h
can temporarily fix this.expression must have a constant value
: If you have the these issues above fixed, you will meet this problem when using CUDA 9 with VS2017. This seems to be an API corruption. Rolling back to VS version older than 2017 15.4 or using toolset v140 may be able to fix this. Two ways to use v140 in VS2017:-T v140
invcpkg_configure_cmake
vsvarall.bat
to set shell environment to use v140, and then use vcpkg to build. (For ports using ninja)Related issues in other repositories are collected here:
I open this issue here to track the avaliability of CUDA support, and provide solution for ones who has faced similar problems.
The text was updated successfully, but these errors were encountered: