Windows Cmake Error: No CUDA toolset found - opencv

I was doing a project about image processing. I installed darknet, OpenCV and NVIDIA GPU Computing Toolkit\CUDA\v10.2. I was able to get build on OpenCV, but when trying to get build on darknet, it gives the following errors and I couldn't find the solution even though I searched for hours.
CMake Error at C:/Program Files/CMake/share/cmake-3.17/Modules/CMakeDetermineCompilerId.cmake:367 (message):
No CUDA toolset found.
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.17/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
C:/Program Files/CMake/share/cmake-3.17/Modules/CMakeDetermineCUDACompiler.cmake:72 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:60 (enable_language)


You need to have both the "development" and "Visual Studio Integration" components installed.
If you have only the first one installed (i.e. you have all you need to develop with cuda) but not the latter, then CMake won't find cuda!
just run the installer again and select "Visual Studio Integration" component (even without reinstalling the rest)


I faced the same problem, by this step you probably have installed the cuda toolkit and visual studio but which one did you installed first?
I recommend installing visual studio 2017 community edition, then reinstall the CUDA toolkit, do not uninstall the current version that you have, this will create the Visual studio support for your cuda. Then at the time of "configure" in CMake, choose Visual Studio 2017 as compiler, I hope this help you.
edit: I used CMake 3.16.0


It is effective to reinstall cuda without uninstalling the original cuda

Related

CMake - could not find any instance of Visual Studio [duplicate]

When I am trying to install CMake I get the error:
Visual Studio 15 2017 could not find any instance of Visual Studio.
I am using Windows 7 and Visual Studio 2017. The CMakeOutput.log file writes:
The system is: Windows - 6.1.7601 - AMD64
Any ideas?

I ran into the same error and performed the following steps to resolve the issue:
Open Visual Studio
Go to Tools -> Get Tools and Features
In the "Workloads" tab enable "Desktop development with C++"
Click Modify at the bottom right
These steps resulted in the "Visual C++ tools for CMake" feature being installed, but the other optional C++ features included in this workload may also helpful for what you are trying to do.
After the Visual Studio updater finishes installing try re-running the command. You may need to open a new command window.

In my case, I installed Visual Studio, selecting the workloads and modules that I wanted, but I ignored the request to reboot, assuming that shutting down the computer at the end of the day and restarting it the following day would suffice. I was wrong.
The following day I tried a cmake build and got the "could not find any instance of Visual Studio" error. After several attempts to resolve, I re-ran the installer, made no changes to the configuration, and clicked Modify. This time I let it reboot the computer. The reboot took a long time. After which my cmake build worked.

If you have already installed the workload Desktop development with C++ and still getting the following errors while using visual studio 2022 for flutter
Generator
Visual Studio 16 2019
could not find any instance of Visual Studio.
Building Windows application...
Exception: Unable to generate build files"
Solution: Follow these steps,
Edit your_flutter_path\packages\flutter_tools\lib\src\windows\build_windows.dart, and change the constant on line 28 from Visual Studio 16 2019 to Visual Studio 17 2022
Delete flutter_tools.stamp and flutter_tools.snapshot from your_flutter_path\bin\cache\
Run flutter clean in the project

I had the same issue "could not find any instance of Visual Studio"
but with Visual Studio 2019 (Community Edition) and I just had to configure the VS160COMNTOOLS variable so that CMake correctly detects Visual Studio.
export VS160COMNTOOLS="/c/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/Tools"
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2016%202019.html)
With Visual Studio 15 2017, the variable you need should be VS150COMNTOOLS.
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2015%202017.html)
NB: in my case, in a Travis-CI workflow, I installed Visual Studio using the commands (no need to reboot):
choco install visualstudio2019community
choco install visualstudio2019-workload-nativedesktop # required
With only the first package, CMake detection of VS2019 failed.

I was configuring a Jenkins build node and could successfully run CMake GUI manually but command line use or builds using the CMake plugin would fail with:
Visual Studio 16 2019 could not find instance of Visual Studio.
-A x64 parameter was added with no change in result.
The problem was that CMake could not determine the Windows SDK version.
By adding CMAKE_SYSTEM_VERSION parameter CMake was then able to find Visual Studio.
-D CMAKE_SYSTEM_VERSION=10.0.18362.0 (use your windows SDK version)
Environment:
windows 10 system build: 19042
CMAKE 3.19.4
VS 2019 Professional 16.8.4
Jenkins 2.235.1
Full command line that worked:
"C:\Program Files\CMake\bin\cmake" -G "Visual Studio 16 2019" -D CMAKE_BUILD_TYPE=Release -A x64 -D CMAKE_SYSTEM_VERSION=10.0.18362.0

When using VS 2017, be aware that this is really VS 2015, and CMake identified it as VS 2017 2022 which is not the version of VS 2017 I had, that gave me this error. So the conclusion I offer is to try different versions, specifically the 2015 one.

I had a similar issue where installing libzmq in my npm project was throwing the same error and that wasn't getting solved by enabling "msbuild" under "Desktop development with C++" in the Visual Studio installer.
My solution ended up being to reinstall the Windows build tools for npm with the following command.
npm install --global windows-build-tools
Note: Remember to run the command prompt (or whatever terminal you are using) as admin before running this.

If the CMake used to work with the installed Visual Studio and is broken someday, then the problem could be VS requires system reboot to complete some update.
For quick verification, rename HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot to like HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot.bak, then re-run cmake which should succeed. Don't forget to rename the registry back and reboot the system if this is the problem.

In my case, I was selecting different version of visual studio in that configuration dialog box whereas I installed different version.
Do select the same version.

Above solutions did not solve this issue for me. After installing node.js from https://nodejs.org/en/download/ apparently a correct version of windows-build-tools was installed

I reinstalled the Visual Studio 2019(my former one is 2017 version ) with all those settings required(my cmake version is 3.23.0),and it works. So try to install different versions.

In my case, the problem was gone after I deleted the previous cmake result directory and then ran cmake again.

if you have installed two or more Windows 10 SDK, delete them excluding latest one.

Try downloading the windows-build-tools package.
npm install --global --production windows-build-tools --vs2015
This step should be the end-all-be-all solution to fixing node-gyp problems. For most people, that’s true. NPM has a package called windows-build-tools that should automatically install everything you need to get node-gyp working, including the Microsoft build tools, compilers, Python, and everything else required to build native Node modules on Windows.

Why vcpkg can't install packages?

When I try to install matplotlib-cpp using vcpkg, the console always returns Computing installation plan..., then nothing happens. After that, I checked the installation package with .\vcpkg list. It seems that this package has not been installed.
I also tried to install other packages and encountered the same situation.
Environment:
Windows 10, 64 bit build 19042
Visual Studio 2019
cmake 3.21.0-rc2
Git
The scene where the problem occurred

We also ran into this. Extremely painful to find as CMake seems to work otherwise. If you use vcpkg at all I would advise not trying CMake 3.21.0 until this is fixed.

Vcpkg Libraries not detected by Visual Studio 2019 Community edition

I am currently working on a Open-Source Project, which has some third-party library dependencies, I have installed all of them using Vcpkg into a particular folder in my E: drive and integrated them with Visual Studio with the "vcpkg integrate install" command, and supplied the Cmake toolchain also in the IDE.
But the libraries (ie. WxWidgets currently) are not being detected while configuring the build.
I am attaching the configuration message as well as the error snapshots below.
Any suggestions regarding this, would of great help.
Thanks & Regards.
buildsnap
ErrorSnap

MSVCP140.dll missing in VS2013 + Win7

I am trying to install OpenCV 3.2.0 and run CannyStill.cpp according to the following instructions.
Installation Cheat Sheet 1 - OpenCV 3 and C++.pdf
I am using VS2013 plus Win7.
I have set the Runtime Library to /MTd.
I have installed VC++ 2015 Redistributables.
but the problem is not going away.
How can I solve the issue?

The problem is that your OpenCV was compiled with another Visual Studio compiler (2015). With the redistributables you will get the release version of the dll, but not the debug one. The error is complaining about
MSVCP140D.dll
which is for debuging.
Possible solutions
You can recompile OpenCV (why is not compiled with the same visual studio in the first place?) with VS2013 and use that one.
Install VS2015 and use that one.
Compile it and run it in release mode.
Choose whichever suits you :)

Cant find package manager console in visual studio for mac

I am using Visual studio for mac. I need to install some packages but I can't find package manager console for that.
Visual studio version: Preview 1 (7.0 build 347)

Warning:
A commenter reports this extension crashes VS Community 2019 for Mac version 8.5 (Build 3183). I haven't upgraded to it, so I can't speak to this. Anyone with information/fix/alternate approach, please chime in down in the comments.
OK:
At least in Visual Studio Community 8.4.8 build 2, you can find it under Visual Studio-->Extensions, using search term "nuget":
It took me so long to find this I hope it helps someone else find it faster!

Similar to Xamarin Studio, you have to use its dialog,
https://developer.xamarin.com/guides/cross-platform/xamarin-studio/nuget_walkthrough/
As there was no cross platform PowerShell, Xamarin Studio lacks of Package Manager Console. It might come one day in Visual Studio for Mac. We will see.

You can follow the NuGet CLI reference and install it
https://learn.microsoft.com/en-us/nuget/tools/nuget-exe-cli-reference
An excerpt from that link provided reads:
macOS/Linux
Behaviors may vary slightly by OS distribution.
Install Mono 4.4.2 or later.
Execute the following commands at a shell prompt:
# Download the latest stable `nuget.exe` to `/usr/local/bin`
sudo curl -o /usr/local/bin/nuget.exe https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
# Give the file permissions to execute
sudo chmod 755 /usr/local/bin/nuget.exe
Create an alias by adding the following script to the appropriate file for your OS (typically ~/.bash_aliases or ~/.bash_profile):
# Create as alias for nuget
alias nuget="mono /usr/local/bin/nuget.exe"
Reload the shell. Test the installation by entering nuget with no parameters. NuGet CLI help should display.

I found a good reference for mac users:
https://github.com/mrward/monodevelop-nuget-extensions
Thanks for the reference and it works for me.

Resources