Closed Stinkfist0 closed 11 years ago
Starting x64 VC9 testing now.
Tested now also with VC9. Should be good to go.
Edit: I'll take it back, there seems to be some problems still, but nothing too big anymore.
Ok, now should be good to go. It would appear that protobuf build can fail on command line, but builds just fine using the VS IDE.
Will begin testing this now.
Fixes #427
64-bit Tundra on Windows tested, built and run successfully using both VS2008 and VS2010 with Boost disabled.
Note/todo: OGG playback not working properly (audio output is distorted static noise) in RelWithDebInfo build (works just fine in Debug). However this problem has been noticed also on 32-bit builds occasionally, although very rarely.
Note: It would appear that when doing a 64-bit VC9 build, some of the dependencies (protobuf at least) can fail on command line. As a workaround, one should be able to build these dependencies just fine using the VS IDE.
Note: After this pull request, the "deps" directory is used only for 32-bit VC9-built deps. All other build configuration variant deps are placed to "deps-%VS_VER%-%TARGET_ARCH%". f.ex. "deps-vs2010-x86". So, if you have already build 32-bit dependencies with VS 2010, remember to rename the "deps" dir to "deps-vs2010-x86", or otherwise the fullbuild script will start building the dependencies from scratch the next time it is invoked.
IMPORTANT: If you have installed VS x64 tools after installing VS SP1 make sure you re-apply the VS SP1 installation before building Tundra and its dependencies as 64-bit!