Compiling under VS2012: Difference between revisions
Jump to navigation
Jump to search
Bug:Converting the Alien Swarm server project to VS2012 will lead to an "invalid characters in path" error. To fix it, open
Bug:Compiling the 2013 code base with any version of VS2012 is not possible at this time. You can, however, use the VS2012 interface with the VS2010 compiler.
No edit summary |
m (Setting bug notice hidetested=1 param on page where the bug might not need tested in param specified) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{TabsBar|main=Visual Studio}} | ||
{{LanguageBar}} | |||
{{Outdated sdk|{{astools|4.1|nt=1}}|newer-sdk-equivalent=[[Compiler choices]]}} | |||
[[File:Visual studio logo.png|right]] | [[File:Visual studio logo.png|right]] | ||
| Line 5: | Line 8: | ||
Using '''Visual Studio 2012''' is possible for Source. However it is not possible to use Visual Studio 2012 with the Source 2013 code base. You can use the free [http://www.microsoft.com/express/Downloads/#2012-Visual-CPP C++ Express] edition for the 2007 code base and below. | Using '''Visual Studio 2012''' is possible for Source. However it is not possible to use Visual Studio 2012 with the Source 2013 code base. You can use the free [http://www.microsoft.com/express/Downloads/#2012-Visual-CPP C++ Express] edition for the 2007 code base and below. | ||
{{bug|Converting the Alien Swarm server project to VS2012 will lead to an "invalid characters in path" error. To fix it, open <code>game\server\swarm_sdk_server.vcproj</code> with a text editor and delete "<code>'
$File</code>" from line 2232.}} | {{bug|hidetested=1|Converting the Alien Swarm server project to VS2012 will lead to an "invalid characters in path" error. To fix it, open <code>game\server\swarm_sdk_server.vcproj</code> with a text editor and delete "<code>'
$File</code>" from line 2232.}} | ||
{{bug|Compiling the 2013 code base with any version of VS2012 is not possible at this time. You can, however, use the VS2012 interface with the VS2010 compiler.}} | {{bug|hidetested=1|Compiling the 2013 code base with any version of VS2012 is not possible at this time. You can, however, use the VS2012 interface with the VS2010 compiler.}} | ||
* With the default VS2012 settings, linking some projects will fail with "Error lnk2026: module unsafe for safeseh image". This seems to happen when you try to link to libraries that were compiled with different versions of the compiler. As a workaround, set the linker option <nowiki>/SAFESEH[:NO]</nowiki> . | * With the default VS2012 settings, linking some projects will fail with "Error lnk2026: module unsafe for safeseh image". This seems to happen when you try to link to libraries that were compiled with different versions of the compiler. As a workaround, set the linker option <nowiki>/SAFESEH[:NO]</nowiki> . | ||
== See also == | == See also == | ||
Latest revision as of 07:16, 20 May 2025
This page was written for 
Alien Swarm Authoring Tools or earlier. It may not be applicable to newer versions of the Source SDK.
For more up-to-date information, see Compiler choices.
Alien Swarm Authoring Tools or earlier. It may not be applicable to newer versions of the Source SDK. For more up-to-date information, see Compiler choices.
Using Visual Studio 2012 is possible for Source. However it is not possible to use Visual Studio 2012 with the Source 2013 code base. You can use the free C++ Express edition for the 2007 code base and below.
Bug:Converting the Alien Swarm server project to VS2012 will lead to an "invalid characters in path" error. To fix it, open game\server\swarm_sdk_server.vcproj with a text editor and delete "'
$File" from line 2232.Bug:Compiling the 2013 code base with any version of VS2012 is not possible at this time. You can, however, use the VS2012 interface with the VS2010 compiler.- With the default VS2012 settings, linking some projects will fail with "Error lnk2026: module unsafe for safeseh image". This seems to happen when you try to link to libraries that were compiled with different versions of the compiler. As a workaround, set the linker option /SAFESEH[:NO] .