@Jacob: MS tends to break their own C++ compilers with each VS release, so I would recommend you to keep using VS2010 for Source SDK; but if you really, really need the new IntelliSense features added in VS2012, you can install 2010 and 2012 in the same machine and the later will use the "old" compiling tools if you refuse to update the project when opening it.
2013/6/27 Jacob "J*Rod" Salas <czfj...@gmail.com> > Hey, I've been building the latest multiplayer code in VS 2012 (Release), > and I immediately run into linker mismatches with _MSC_VER (1600 vs 1700) > in pretty much every precompiled library. I probably should've just built > the project using the 2010 toolset to begin with, but I don't think those > files had any compatibility problems like that in any other SDK. > > Thanks! > > -- > Jacob "J*Rod" Salas > The star is silent, but prominent... <http://jsmedia.tk> > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders > > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders
