The first step was to set up my development environment for 64 bit development. I use Visual Studio 2003 which has little built in support for 64 bit development.
In order to create 64 bit applications you need to install the latest Platform SDK from Microsoft (Microsoft Platform SDK for Windows Server 2003). The SDK, as well as having libraries for 32 bit programming, has 64 bit versions for AMD64 and IA64 (Intel) development.
Getting the correct library and header file paths set up in Visual Studio proved surprisingly difficult. I wanted the choice of developing 32 bit or 64 bit projects. While the platform SDK comes with command files to set up the correct paths they wipe out any other paths. Since T2 uses DirectX I also needed the DirectX paths setting correctly.
Upgrading to a newer edition of Visual Studio looks like the safer, non-hackish solution, if possible.
As Warren points out, this isn't easy with VS2003. You need to install the x64 compiler from the platform SDK.
We ran this way for a couple of years (starting with even earlier versions and the IA64 compiler). There were separate project configurations for X64 builds, so in addition to the normal DEBUG and RELEASE configurations we had DEBUG_X64 and RELEASE_X64.
But you have to launch VS studio with the paths set up for either the x86 or x64 compilers & libraries. You couldn't switch between them on the fly. I believe there was a command line switch /useenv that told VS to set its various paths from environment variables. We had bat files to set this all up.
It is messy, and every now and then we'd build the wrong project configuration for the environment which always took a while to sort out. You are much better off upgrading to VS2005/VS2008 where the target architecture is exposed directly in the GUI.
发布评论
评论（3）
有关 2003 年缺少 64 位目标的此页面似乎可以解决您的问题： http:// www.toymaker.info/Games/html/64_bit.html。
如果可能的话，升级到 Visual Studio 的新版本看起来是更安全、非黑客的解决方案。
This page on 2003's lack of 64-bit targeting seems to address your issue: http://www.toymaker.info/Games/html/64_bit.html.
Upgrading to a newer edition of Visual Studio looks like the safer, non-hackish solution, if possible.
正如 Warren 指出的，这对于 VS2003 来说并不容易。 您需要从 平台 SDK。
我们以这种方式运行了几年（从更早的版本和 IA64 编译器开始）。 X64 构建有单独的项目配置，因此除了正常的 DEBUG 和 RELEASE 配置之外，我们还有 DEBUG_X64 和 RELEASE_X64。
但是您必须启动 VS studio，并为 x86 或 x64 编译器设置路径。 图书馆。 你无法在它们之间即时切换。 我相信有一个命令行开关 /useenv 告诉 VS 从环境变量设置其各种路径。 我们有bat 文件来设置这一切。
它很混乱，我们时不时地会为环境构建错误的项目配置，这总是需要一段时间才能理清。 最好升级到 VS2005/VS2008，其中目标架构直接在 GUI 中公开。
As Warren points out, this isn't easy with VS2003. You need to install the x64 compiler from the platform SDK.
We ran this way for a couple of years (starting with even earlier versions and the IA64 compiler). There were separate project configurations for X64 builds, so in addition to the normal DEBUG and RELEASE configurations we had DEBUG_X64 and RELEASE_X64.
But you have to launch VS studio with the paths set up for either the x86 or x64 compilers & libraries. You couldn't switch between them on the fly. I believe there was a command line switch /useenv that told VS to set its various paths from environment variables. We had bat files to set this all up.
It is messy, and every now and then we'd build the wrong project configuration for the environment which always took a while to sort out. You are much better off upgrading to VS2005/VS2008 where the target architecture is exposed directly in the GUI.
听起来像是一个可行的解决方案......在接受答案之前先尝试一下。 投票了！
温迪
Sounds like a viable solution... going to try it before accepting the answer. votes up!
RWendi