Lucas,
Yesterday it was the first day that I put my hands on Borland bcc 64 and it is quite different from bcc 32. First of all, the download/setup for the Embarcadero's demo, is simply daunting. Its huge!!! even if you unselect many packages not needed by us.
One of those differences is that LIB files are no longer used. Not with that sufix. It seems as they use ".a" like in Linux. Also if you run bcc 64, there is no help on screen as it used to be. Really shocking...
Said that, I think it is very clever to consider a migration to Microsoft C, that at least, it is exactly the same for 32 and 64 bits. And thats a really help
Anyhow, I will continue reviewing bcc 64, maybe its easy after a scaring first review
![Smile :-)](./images/smilies/icon_smile.gif)
Related to your answer:
In runtime you can use FWH function IsWin64() to check if you are running on a Windows 64 bits. In compile time, there is no way to distinct Harbour 32 and 64 (unless I am wrong) though you can use a define from the batch file that invokes your makefile. From C code you can use:
#ifdef _WIN64
and to detect the C compiler:
- Code: Select all Expand view
#ifdef __BORLANDC__
asm push ax;
#elif defined( _MSC_VER )
_asm { push ax }
#elif defined( __GNUC__ )
asm( "push ax" );