I need to compile some CUDA code with MSVC2010 but I might consider buying MSVC2012 instead of MSVC2010 if I can switch toolset to 10 from MSVC2012 options.
Is that possible or MSVC2012 just ships with the 11 toolset?
As noted in the comments, you can only get the v100 toolset in VS2012 if VS2010 was already installed on the machine. So high odds that you'll need to choose VS2010 if the Cuda tool-chain you use doesn't support VS2012 yet.
A quick google turned up this blog post, showing you how to setup VS2012 to run the NVidia Cuda 5.0 tool-chain. It isn't clear from your question whether this applies. Do take a look at this, VS2012 is an excellent VS2010 service pack ;)
Related
We are currently using CUDA on windows which requires MS C++ Build tools installed. With every new version of the CUDA toolkit it happens that newer versions of Visual Studio are not supported. That's why we are using the MS build tools seperately so that the VS version doesn't matter.
Since its hard to guide our developers to install the right CUDA and MSVC version we have packaged it into NUGET packages so that the toolkit (especially NVCC) is in a defined version and location. Additionally we wanted to do this with MSVC but we couldn't find a good solution since the installer obviously does modifications on several places that we don't know.
Is there any good way to get the MSVC tools portable so that we can simply drop it into a folder and put the right pathes?
NVCC doesn't support GCC, otherwise I would have gone with this.
I am working on Windows 7, Visual studio 2010.
Can we debug cuda code using single GPU which also providing display to the monitor in the same PC?
What tools are available ? NSIGHT seems to be working with two GPUs.
Windows 7 support has been dropped in newer versions of Nsight, (see here) basically anything that was released in 2020 or newer. So you're stuck with older versions. Older versions will also have a support chart like the one I previously linked which explains the supported debug scenarios. Generally speaking, single GPU debug as you describe should be possible with a "newer" GPU like Kepler or newer.
The last Nsight version that supported Win 7 is 2019.4 and the associated documentation indicates support for single GPU debugging.
Note that in the 2019.x timeframe, the Nsight tools had both a "legacy" and "next gen" debugger, and the one you should use will depend on which GPU you are using (and possibly driver model WDDM/TCC), see here.
Also note that the last CUDA toolkit that had official support for VS 2010 was in the CUDA 9.x generation.
This question already has an answer here:
LLVM 7.0 does not provide specific Platform Toolset on Visual Studio 2015
(1 answer)
Closed 3 years ago.
Using clang 6.0.1 I can create MSVC projects with LLVM-vs2014 toolchain to build them with clang.
Clang 7.x and 8.x seem not to include such a toolchain. Is the feature deprecated, unsupported, or is there just another way to use it?
I does seem that the VS specific toolchains are not included in the later releases of Clang. You can always check what build tools are available by right clicking your project in VisualStudio selecting Properties and then look under Platform Toolset:
Another option is to use this visual studio extension which should allow you to use an existing installation of clang you have on your machine.
Finally, starting with Visual Studio 2017, there is an experimental version of Clang that you can use as a platform toolset called Clang/C2. You'll need to run the Visual Studio Installer to ensure that you have installed it, but otherwise it should show up in the platform toolset as v141_clang_c2 as shown in the image above.
Edit: As per the comment below, it seems that Clang/C2 has been abandoned and is no longer a good, long term option.
I've spent a lot of time in the past trying to get newer versions of clang to play nice with Visual Studio and it hasn't been fun (or fruitful). Hopeful this type of support gets better in the future. As a side note, if you're not generating solution files with CMake and instead use Visual Studio "Open Project" feature for CMake based projects, you may be able to manually set CMAKE_CXX_COMPILER and CMAKE_C_COMPILER to force the use of Clang.
Considering to develop a desktop application with Qt for Windows. It will be a free download application, but for a commecial SERVICE. (need an account with our commercial service to work).
I think we could use the Qt for Windows from Nokia (LGLP version) because its free app. But the lastest one version of Qt needs a C++ complier from Microsoft.
Which one?
Do I need to pay for an C++ compiler from Microsoft, or do they have a free version to use with Qt?
Reading info docs, googling and we still cann't understand what tools do I need.
If you want to use the Visual Studio compilers, you can download the free Windows SDK. The following link takes you to the SDK for Visual Studio 2008:
Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1
This includes all the C++ compilers and tools you need. (There is a more recent version available, but Visual Studio 2010 is not yet a "level 1 supported" platform for Qt.) We are using this on standalone build machines and it works fine.
Just a personal opinion, but we have found that using anything other than MSVC on Windows (for example, MinGW) causes a lot of problems. It is not that the other toolchains are bad, it is just that they are all treated as second-class citizens. We had lots of problems with third-party libraries not being able to build in MinGW or having nonexistent build instructions and having to do a lot of manual Makefile editing, etc. You are much more likely to have things "just work" if using MSVC.
For the most part (static linking), you cannot mix and match. You need to pick one toolchain and stick with it. If I were starting from scratch, I'd definitely go with MSVC.
Just our experience (we started with MinGW); your mileage may vary.
No, you do not need to pay for anything.
The Microsoft toolchain is available for free as part of the Microsoft Windows Software Development Kit.
Additionally, the following article may also be of interest to you:
Developing Windows Applications in C++: The tools you need
The alternative supported by Qt is MinGW. The runtime libraries are free from copyright, so you can do whatever you want with them.
It is basically the Windows counterpart of the GNU Compiler Collection (GCC) under Unix.
Can someone give me a link where i can download a gtkmm 3.0 library for development without need to build it by myself?
thanks
http://live.gnome.org/gtkmm/MSWindows
That is the best I could find. It stops at 2.8, tough.
http://mail.gnome.org/archives/gtkmm-list/2011-April/msg00077.html
That is an email to the gtkmm mailing list from the windows installer developer. It seems that the dev doesn't have much time for it right now (or at least didn't on April 28, 2011).
Not much help, but that seems to be the state of gtk+ and gtkmm on windows right now.
The original question is old, but I post here for future visitors.
Apparently the link specified in senshikaze's answer is broken.
Windows installer (for both runtime and development stuff) is available from ftp.gnome.org
32-bit
64-bit
I built the gtkmm binaries over official gtk 3.6.4 binaries.
For 32 bit version you can download the binaries that I created, and there is also the (simple) procedure to create them yourself if you need 64 bit, everything on http://www.giuspen.com/2014/02/build-gtkmm-3-6-0-windows-binaries-on-official-gtk-3-6-4-bundle/
Gtk 3.0 library for windows is at hand from http://www.gtk.org/download/win32.php/
And you could find more optional dependence on http://win32builder.gnome.org/
But Gtkmm 3.0 hasn't have an official release, but some volunteer make it, I find a good one, http://sourceforge.net/projects/tview/files/gtkmm_bin_3_6.7z/download
I created a blog on how to install latest gtkmm on Windows (step by step) here:
http://gtkmm-installation.blogspot.com/
UPDATE:
I have just compiled everything with Visual Studio, You can download my gtkmm3 development binaries for Windows x64 from my GitHub page, I also made a wiki entry on how to compile everything on your own with Visual Studio.
All of the Visual Studio projects to compile everything can also be found on GitHub.
You can install it with vcpkg.