This is not an issue per se, as I managed to make things work with CUDA 10, but I wanted to report some incompatibilities with the latest CUDA 11, to avoid anybody else getting stuck (NVIDIA GeForce GTX 1650 and Win10).
(1) Kepler architectures (sm_30) are dropped from CUDA 11, so line 105 in the top level CMakeLists.txt file throws up an error. This is easily changed, though.
As mentioned, everything built as expected after downgrading to CUDA 10.
I also attempted a build with Visual Studio 2019 Community and CUDA 11, which was successful in that the build was seamless and error-free, but the demos returned unexpected results (e.g. see attached the figure returned by the cgsense_brain32ch_recon_2D script). I assume this is as expected, which is why you explicitly state that VS 2013 is required, right? It's only that I expected it to fail in another way.
Hi Andy,
This is not an issue per se, as I managed to make things work with CUDA 10, but I wanted to report some incompatibilities with the latest CUDA 11, to avoid anybody else getting stuck (NVIDIA GeForce GTX 1650 and Win10).
(1) Kepler architectures (sm_30) are dropped from CUDA 11, so line 105 in the top level CMakeLists.txt file throws up an error. This is easily changed, though.
(2) The more severe incompatibility is that CUDA 11 no longer supports integration with Visual Studio 13 (see Table 2 in https://docs.nvidia.com/cuda/cuda-installation-guide-microsoft-windows/index.html ).
As mentioned, everything built as expected after downgrading to CUDA 10.
I also attempted a build with Visual Studio 2019 Community and CUDA 11, which was successful in that the build was seamless and error-free, but the demos returned unexpected results (e.g. see attached the figure returned by the
cgsense_brain32ch_recon_2D
script). I assume this is as expected, which is why you explicitly state that VS 2013 is required, right? It's only that I expected it to fail in another way.Cheers, Sam