Hi Michael
I thought that brook_d.exe add some debug feature to the output code. It seems that this is not the case.
This is the Micosoft server 2003 R2 platform SDk released on March 2006. It is supposed to build apps for x86, x86_64 under Windows XP 32, x64 and Windows 2003 server:
http://www.microsoft.com/downl...19ca0d&displaylang=en I have used it successfully to build apps on 32b XP, using Brook+. I am using both VS2005 & batch files. The batch files use command lines copied from Brook+ samples under vs2005
It has a whole binary branch for AMD64 architecure (cl.exe, link.exe, lib.exe). The directory path under the sdk is:
Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64\x86\AMD64
The binaries (cl.exe, lib.exe, link.exe) that come with vs2005 express do not launch from vs2005 under xp64
The same applies for Lib & Include Directories:
Microsoft Platform SDK for Windows Server 2003 R2\Lib\AMD64
Microsoft Platform SDK for Windows Server 2003 R2\Include\crt , same...\sys
I used the above SDK paths successfully to port 32b linux apps to windows x64/AMD64. The only issue is with linking to brook+.
I believe for settings you use /D_WIN64 (or possibly /DWIN64), and /D_AMD64 for compiler, and for linker /MACHINE:AMD64.
I will have to make sure I am having a path for CAL 64 (I assume the installation automatically did that).
Maybe if you just tell me the official procedure for linking a Brook+ application to a 64b code compiled under XP x64 as "64b", I will just follow yours
Thanks
Amr