MSC64 build requires HB_ARCH setting, otherwise it defaults to w32:
For your convenience xHarbour's bin directory was added to your PATH. Defaulting HB_ARCH to w32.
For your convenience cl's bin directory was added to your PATH
Creating System Files (ST) ...
NMAKE : fatal error U1077: 'e:\fw\temp\msc64\msc\bin\CL.EXE' : return
code '0x2'
Stop.
Is there a way to avoid this?
MSC64 build requires HB_ARCH setting, otherwise it defaults to w32:
For your convenience xHarbour's bin directory was added to your PATH.
Defaulting HB_ARCH to w32.
For your convenience cl's bin directory was added to your PATH
Creating System Files (ST) ...
NMAKE : fatal error U1077: 'e:\fw\temp\msc64\msc\bin\CL.EXE' : return
code '0x2'
Stop.
Is there a way to avoid this?
VS uses the same exe to compile 32bit and 64bit - the only way to detect
what the user want is an internal VS setting %is_x64_arch% - so you have
to set either xHarbour's HB_ARCH or VS' is_x64_arch to indicate your
wish.
Il 19/01/2024 16:01, Ron Pinkas ha scritto:
MSC64 build requires HB_ARCH setting, otherwise it defaults to w32:
For your convenience xHarbour's bin directory was added to your PATH. Defaulting HB_ARCH to w32.
For your convenience cl's bin directory was added to your PATH
Creating System Files (ST) ...
NMAKE : fatal error U1077: 'e:\fw\temp\msc64\msc\bin\CL.EXE' : return code '0x2'
Stop.
Is there a way to avoid this?
VS uses the same exe to compile 32bit and 64bit - the only way to detect what the user want is an internal VS setting %is_x64_arch% - so you have
to set either xHarbour's HB_ARCH or VS' is_x64_arch to indicate your
wish.
Can we test the existence of ml64.exe?
Can we test the existence of ml64.exe?
Yes, I will try to add in my next xHarbour work session - must go back
to normal work :)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 20:09:19 |
| Calls: | 10,390 |
| Calls today: | 1 |
| Files: | 14,061 |
| Messages: | 6,416,974 |