Is Cuda 6 supported with Visual Studio 2013?
If not, is there a hack to make the two work with each other?
I see lots of value in upgrading to VS 2013 as it (VC++) better implements the C++11 standard, and to CUDA 6 for its unified memory architecture, and other improvements.
What is officially supported for CUDA 6 is listed in the cuda-getting-started-guide-for-microsoft-windows pdf document, which is installed with the CUDA 6 toolkit.
VS2013 is not officially supported with CUDA 6. VS 2013 is officially supported with CUDA 6.5, which can be verified from the corresponding document installed with CUDA 6.5 toolkit.
This is September 2014, and the production Release of Cuda 6.5 is out, and it works with Visual Studio 2013. No other version of Cuda works with Visual Studio 2013.
CUDA 6.5 works with Community Edition 2013 ("new Express", but with more support like MFC and even for small enterprises for free).
Sorry that I could not comment.. I have not 50 reputations -,- Would kindly thank you all for reputations to support the community here in the future :)
Related
Since the very beginning of the release of Visual Studio 2017, it seems there has been two differentiated branches:
- 15.0
- 15.x
In the above link you can see that 15.0.0 and 15.1 Preview 1 were released the same day, and then there were updates for 15.0 and 15.x. At the date of this question, latest versions are 15.0.21 and 15.9.11
What are the differences between these two development branches?
In general Microsoft offers a dual support model for most of these tools:
Stay on RTM/RTW. Basically the 15.0.x version. This version will receive hotfixes, but no feature improvements and is a Long-Term-Support version. This version is generally only available through Visual Studio subscriptions and can only be downloaded from https://my.visualstudio.com.
Stay on the latest version. Basically the 15.x.x version. This version will receive hotfixes and feature updates at a regular interval until the next major version (2019) is released. Support is normally only given on the latest update version, so if you have issues, you're likely going to be asked to upgrade to the latest 15.x.x version to see if the issue persists.
The same applies to Azure DevOps Server / Team Foundation Server.
Release notes for Visual Studio 2017 15.9.x can be found here.
Release notes for Visual Studio 2017 15.8.x can be found here.
Release notes for Visual Studio 2017 15.7.x can be found here.
Release notes for Visual Studio 2017 15.6.x can be found here.
Release notes for Visual Studio 2017 15.5.x can be found here.
Release notes for Visual Studio 2017 15.4.x can be found here.
Release notes for Visual Studio 2017 15.3.x can be found here.
Release notes for Visual Studio 2017 15.2.x can be found here.
Release notes for Visual Studio 2017 15.1.x can be found here.
Release notes for Visual Studio 2017 15.0.x can be found here.
In general you get more features, improvements and fixes in the 15.x.x version. But you may have to upgrade your solution from time to time to stay current with the tooling.
You get fewer impacting changes and a longer support window by staying on 15.0.x.
I would like to make an app for my Lumia stuck on Win 10.0.14393 (or 1609) using C++/WinRT. I've created a Blank app project with
Target platform version: 10.0.17134.0 and
Target platform min. version: 10.0.14393.
The project fails to compile with the following errors:
error C2039: 'DisconnectUnloadedObject': is not a member of 'winrt::BlankApp2::implementation::MainPageT'
error C2039: 'UnloadObject': is not a member of 'winrt::BlankApp2::implementation::MainPageT'
Is this a bug or intentional behavior? Please note, that setting any newer min. version results in successful build.
The latest version of C++/WinRT can support all versions of Windows 10, including 14393 and older versions as well.
Keep in mind that C++/WinRT is both a library and a language projection. The language projection provides access to Windows APIs targeting a given version of Windows. Each version introduces new APIs. So if you want to target a minimum version of Windows, you need to ensure that you limit yourself to the APIs available on that version of Windows. I would however recommend using the latest compiler and the latest Windows SDK as they include many bug fixes.
I suggest you use Visual Studio 2015 when targeting older C++/WinRT and Windows 10 updates. My impression is that most of those were delivered on top of Visual Studio 2015 with Visual Studio 2015 updates and Windows 10 SDK updates and C++/WinRT updates.
When using Visual Studio 2015 with C++/WinRT, you will need the latest update, Update 3. Check for updates and make sure that your copy of Visual Studio 2015 has the most recent updates. I was just using an install of Visual Studio 2015 Enterprise to recompile something that compiles fine with Visual Studio 2017 and found that I was missing tools and SDKs including for Win 10 SDK 10.0.14393 that were in the Update 3 which I had not yet installed.
You can also go to Programs and Feature from within Control Panel, look for Microsoft Visual Studio 2015 in the list and then do a right mouse click and Change which will allow you to check what is installed and change anything.
Working with C++/WinRT over the last few months I have used both the Visual Studio 2017 Community Edition and the Visual Studio 2015 Enterprise Edition.
I have seen differences when moving a solution from VS 2015 to VS 2017 that required me to review the Properties page of the solution. See also the discussion in synchronizing SDK with Windows 10 update and using WinRT with Standard C++
Working with the latest Windows 10 updates and VS 2017 works best for me because I am able to target the recent Windows 10 updates. However I have found that trying to target older Windows 10 updates with VS 2017 can be problematic.
I'm sorry that I can not be more specific. This whole area of C++/WinRT and Windows 10 updates has much more cowboy than I would like though it now seems to be settling down.
C++/WinRT is a template library that was originally an open source project on GitHub. My impression is that Microsoft has acquired it and it is now a standard product offering. I believe there was a significant rewrite of C++/WinRT at one time as the Visual Studio 2015 and then Visual Studio 2017 moved to implement more of the C++17 and proposed C++20 standards and the Technical Specifications for coroutines.
This seems to be an area still changing to some extent. However most of the changing was going on with VS 2015 and the early VS 2017 along with the SDKs. It seems to be pretty solid now with the latest updates.
So I was trying to install the Intel C++ Compiler (in the Parallel Studio XE 2018 bundle) and when I go to install it comes up with the warning "Intel C++ Compiler will not work because none of the supported environments is found on your computer," among others. However, one of those supported environments is Microsoft Visual Studio 2017, which I have installed.
I read online that there's some issue with the most recent versions of Visual Studio and that the compiler only works with versions 15.6 and below. I have 15.5.6, but of the Community version. I'm not sure if the Professional version is required; if it is I don't have it installed and I can't figure how to install a previous version.
If there is no way to make this work (or there is, but it's too much of a pain), suggestions for other C++ compilers would be appreciated.
You could see this document about “Troubleshooting Fortran Integration Issues with Microsoft Visual Studio*”：
https://software.intel.com/en-us/articles/troubleshooting-fortran-integration-issues-with-visual-studio/
It shared the version of Visual Studio that is supported by the Intel Parallel Studio XE now.
I understand that Cuda 6 does not work with Visual Studio 2013. But shouldn't Cuda 5.5. or Cuda 4.2 work with Visual Studio 2013?
I have Cuda 4.2, 5.5 and 6 installed. If I right click on VS project, and select Build Customizations option, I only see Cuda 6 listed. For Cuda 6, it tells me that I must choose the older v11 toolset, and the other two toolkits are simply non existent.
Is there any way to get Cuda to work on VS 2013?
The supported visual studio versions are listed in the windows getting started guide or toolkit release notes for each CUDA toolkit release.
The CUDA 6 getting started guide is here.
The only toolkit that officially has support for VS 2013 at this time is CUDA 6.5RC available for download to registered developers.
I use MS Visual Studio 2012 for Windows Desktop (C++) and I've recently started using C++11 features,such as range-based for loop,lambda functions,final,override and so on.
But I cannot use some of the features,like std::initializer_list,user-defined signatures...
I don't understand why this version of MS Visual Studio does support some,but not all of them.
Should I start using a newer version,or what?
Thanks.
Yes, you should start using a newer version, because as it happens, newer versions implement new features.
Also, your question doesn't really ask a question.
You can find comparison tables of supported C++11 features in recent versions of Visual Studio on the MSDN website: http://msdn.microsoft.com/en-us/library/hh567368.aspx