Compiling x64 code in VC++ 6.0?

Hi,
I know VC++ 6.0 came out way before x64, but is it even remotely possible to compile an x64 DLL on VC++ 6.0?
All our projects are for VC++ 6.0 and somehow a developer (who left the company) managed to compile an x64 DLL. I'm wondering how he did it? Some other developers say he used a .mak file rather than the .dsp & GUI; and in the .mak file I do see "_M_AMD64" defined, but surely that by itself couldn't allow VC++ 6.0 to create an x64 DLL?
Is it possible he may have just used a newer VC++ to compile the .mak file and have it still be binarily compatible with the other 6.0 binaries?

If you install Windows SDK (the latest version compatible with VC6 is February 2003) - you will get the possibility to select Win64 as target

Quote:

---

Originally Posted by vart

If you install Windows SDK (the latest version compatible with VC6 is February 2003) - you will get the possibility to select Win64 as target

---

But how is that even possible with VC++ 6.0? Doesn't it need to know about the new Rxx registers, 8-byte pointers...? Or is it good enough just to link against 64-bit libraries?

Quote:

---

Originally Posted by cpjust

But how is that even possible with VC++ 6.0? Doesn't it need to know about the new Rxx registers, 8-byte pointers...? Or is it good enough just to link against 64-bit libraries?

---

SDK provides updated compiler - it is a reason you have to place its bin directory before the VC6 native bin directory

OK, now this is strange...

I ran:

Code:

---

SetEnv.cmd /X64 /RETAIL

---

in the Platform SDK directory, then when I run NMAKE on my .mak file I get this error:

Code:

---

tempfile.bat
Access is denied.
        0 file(s) copied.
The system cannot find the file specified.
NMAKE : fatal error U1077: 'tempfile.bat' : return code '0x1'

---

What in the world is tempfile.bat and why is it looking for it?

Just a random guess: have you tried using "nmake -v" to see what nmake thinks it should be doing?

--
Mats

Quote:

---

Originally Posted by matsp

Just a random guess: have you tried using "nmake -v" to see what nmake thinks it should be doing?

--
Mats

---

You mean NMAKE /N /F project.mak ALL?
That gives me:

Code:

---

tempfile.bat
del tempfile.bat

---

EDIT: nevermind. It wasn't building anything because I already had a previous x86 build sitting in the Release directory. Doh!

I must confess it was a long time since I used nmake, and I though it was more similar to the gnu/generic make that I've used more recently.

My nmake (from vc6) says that it's got a /Y to "Disable batch mode". Perhaps that will help?

Or perhaps /D to "display build information, or /P "display nmake information".

Sorry if this is not very useful....

--
Mats