source-sdk-2013
source-sdk-2013 copied to clipboard
ValveSoftware
VPC does not support Visual Studio 2015
I have moved to using VS 2015, but unfortunately the "createallprojects.bat" file does not work for me because VPC does not have a mode for 2015. I was able to generate a 2013 solution by manually adding the "DefaultProjectExtension" registry values, but it does not work in VS 2015 because Visual Studio is seemingly terrible at converting solutions. Either that or the generated solution is missing needed elements of VS 2013 (beyond the extension registry values), which I do not have installed.
Haha :P
Effectively though, Microsoft is already pretty much pushing 2015 as the current version on the Visual Studio website and so on, and it is in the release candidate stage now.
The real problem is that valve hardly ever looks in here anymore let alone update the repo, so my guess is we'll have to wait at least 2 years for such an update~
Idk about the VS 2015 but all previous VS versions converted solutions very well. If you're having trouble generating the solutions you may want to try to install the VS 2013 Express and try again.
On 6/12/2015 11:27 AM, Austin Jones wrote:
I have moved to using VS 2015, but unfortunately the "createallprojects.bat" file does not work for me because VPC does not have a mode for 2015. I was able to generate a 2013 solution by manually adding the "DefaultProjectExtension" registry values, but it does not work in VS 2015 because Visual Studio is seemingly terrible at converting solutions. Either that or the generated solution is missing needed elements of VS 2013 (beyond the extension registry values), which I do not have installed.
— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/source-sdk-2013/issues/325.
I was able to generate a 2013 solution by manually adding the "DefaultProjectExtension" registry values.
~~Which registry? I though the way to make VPC generate vs2013 projects is by adding "/2013" to the line in createallprojects.bat~~ EDIT: Add "/define:VS2013" which will change your toolset from "v100" to "v120_xp" (as defined in source_win32_base.vpc)
~~(Even though a bit buggy, I can compile the resulting project files with vs2015)~~ EDIT: I confused the two Visual Studios.
Which registry? I though the way to make VPC generate vs2013 projects is by adding "/2013" to the line in createallprojects.bat
should it be something like this? devtools\bin\vpc.exe /hl2 /episodic +everything /2013 /mksln everything.sln
There seems to be a lot of issues with building the SDK with VS2015. Surely I'm not the only one that's experiencing these problems?
You are not. On Sep 6, 2015 5:19 PM, "scart" [email protected] wrote:
There seems to be a lot of issues with building the SDK with VS2015. Surely I'm not the only one that's experiencing these problems?
— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/source-sdk-2013/issues/325#issuecomment-138097413 .
Did no one find a work around? I'd rather not install VS2013 again. Otherwise I guess I'll have to get this stuff setup with 2013 and then built it with 2015?
Even if you get the project set up in VS2015, you'll still have to use the VS2013 (or lower) compiler tools. Due to ABI changes, the precompiled static libs are not compatible with VS2015.
I compile Alien Swarm mod with VS2013 but all its static libs are built with VS2005. It works fine for now. Do I risk to have undefined behavior? Should I compile with VS2005 to be on safe side?
I believe you are alright, since most of the changes there affect ABI with the standard libraries. Valve uses that extremely sparingly, in favor of their own classes. VS 2015 shuffled around some built-in functions across libraries, which is what causes linker errors now, even if you tell it to bypass the library compiler version check with a define (which SDK 2013 already uses).
Bumping this because Microsoft is really making a push to get everyone on the latest version of Visual Studio by making it harder to find a download link.
A good portion of the comments on my tutorial on youtube and steam are in regards to Visual Studio or the problem they are having is because they used 2015
I don't see this happening. The code does not compile with VS2015 anyway, and it'd require Valve to update their code.
I can sit down and sort through the code, see what needs to be fixed, but I'm assuming some issues lie within Source code only available with a VDN subscription. Still, if I can get this running, even if it's a bit hackish, it'll at least get us somewhere before the Source 2 SDK is released.
@Foxtrek64 I don't think you'll have much luck with it. See below.
@Nerus87 there isn't. Valve needs to recompile some of their libraries with the 2015 compiler. Most of these libraries aren't in the SDK. @Nephyrin any chance we could get the source for the libraries so we can take care of the SDK ourselves?
I think this engine R.I.P right now, Valve is not interested to continue improve or even fix bugs.
THX.
Microsoft has recently taken down all downloads of Visual Studio 2013 unless you're in the Dev Essentials program. This basically means the Source SDK is now impossible to develop with if you're a newcomer.
The Dev Essentials program has no cost and takes less than 30 seconds to sign up for if you already have a Microsoft account (which was already required for the free VS 2013 editions).
Pretty impossible indeed.
Jordon Moss wrote:
Microsoft has recently taken down all downloads of Visual Studio 2013 unless you're in the Dev Essentials program. This basically means the Source SDK is now impossible to develop with if you're a newcomer.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/source-sdk-2013/issues/325#issuecomment-252054061, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzhVgQxb6_Z6KquB6Y4ft_E35Phjx-wks5qxUJ2gaJpZM4FAyLK.
I wasn't aware, when I tried to go to the page it was bugging out in my browser. I assumed it was a paid subscription-only thing like MSDN, or a program for registered businesses.
It appears that Visual Studio Community 2013 is still available.
You should be able to download it at this address, from official microsoft servers.
In addition, I uploaded the installer to my Source SDK 2013 fork, in case it completely disappears from their servers.
Visual Studio Community 2013 Update 5
I do hope this helps.
Will changing toolset work as told in Source SDK 2013 Getting Started page?
Although Source SDK 2013 currently does NOT compile with Visual Studio 2015 (bug report) you can still use VS 2015 as IDE and compile the code with the VS 2013 toolset.
How to: Modify the Target Framework and Platform Toolset of Visual Studios
@kinnngg
Yes, but you will need to switch to the v120 version of the toolset.
You require to have the v120 toolset installed. If not, you will need to download it from their servers. Once this is done, open up games.sln or everything.sln with the IDE of your choice.
When you open up for the first time, a project that was created in a previous version of VS, you will be prompted to update it's toolset. In this case, you should choose Not to update it.
In case you updated projects, then open up the properties (right click in solution explorer), and in the main configuration layout, find Platform Toolset, it should be v140 in 2015 and v141 if you are using the 2017 RC version. In the list there should be Visual Studio 2013 (v120). Select it.
You should then be able to compile it.
@malortie
I have chosen "Not to update" but it's showing errors when I try to compile in VS2015. How can I change toolset coz there is no option to change Platform Toolset in Configuration Menu :(
Thanks
@kinnngg
Do you have Visual Studio 2013 installed? If not, the toolset cannot be found, which is the reasons you are experiencing issues.
Unfortunately, it was removed from their servers. The only way to have it is to obtain it via Microsoft dev essentials, as stated by users above.