HDK, H9 and VC2005 on WIN64

   4346   4   0
User Avatar
Member
166 posts
Joined: Feb. 2006
Offline
Any weird settings we should be aware of? Cause for win32 it was pretty straight forward, while now it seems it needs some specific settings?
Any help would be appreciated.
Cheers
Time to get out of this messy world.
User Avatar
Member
166 posts
Joined: Feb. 2006
Offline
Ok… so it needs to have the MSVCDir define, and the path C:\Program Files\Microsoft Visual Studio 8\Common7\IDE in the variable PATH.
But why hcustom will go and look for my include (the VC ones) in $HFS/toolkit/include/htools?
Time to get out of this messy world.
User Avatar
Member
13 posts
Joined: July 2005
Offline
Yep, ok, other issues.

I'm getting a lot of linking problems, how on earth do I modify the compiler flags for hcustom?

It looks like it's trying to compile an x86 target with x64 libraries;
libCHOP.a(libCHOP.dll) : fatal error LNK1112: module machine type ‘x64’ conflicts with target machine type ‘X86’

Isn't this just a case of specifying /MACHINE:X64 or have I missed something larger?
User Avatar
Member
12 posts
Joined:
Offline
Hi Kyoseki,
just use the vcvarsamd64.bat inside $MSVCDir/bin/amd64 before to use hcustom.

Cheers
User Avatar
Member
7725 posts
Joined: July 2005
Offline
Le_monkey_butt
But why hcustom will go and look for my include (the VC ones) in $HFS/toolkit/include/htools?

This has always been the case. Those include files are there to make it easier to compile across different platforms.
  • Quick Links