Experiences from convert to 64Bit BCC

Experiences from convert to 64Bit BCC

Postby byte-one » Thu Mar 31, 2016 9:52 am

I will tell to all my way to 64 Bit. Maybe this is interesting for other users.

At begin the parameter -v should apply to BCC64.exe. There comes some interesting information from the compiler (double directories, etc.).
To own c-files should be added the fwh.h and all constructs "( HDC ) hb_parnl( param )" should now be wrote as "( HDC ) fw_parH( param )" to be compatible.

..will be continued....
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria

Re: Experiences from convert to 64Bit BCC

Postby Antonio Linares » Thu Mar 31, 2016 10:06 am

thanks for your feedback
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42074
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain

Re: Experiences from convert to 64Bit BCC

Postby byte-one » Thu Mar 31, 2016 4:40 pm

I found, that for prgs the Harbour-compiler should not make c-files. Unstead the files has to be cpp!
Many errors if using #pragma begindump and #pragma enddump contains cpp-code are gone!
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria

Re: Experiences from convert to 64Bit BCC

Postby Antonio Linares » Thu Mar 31, 2016 4:52 pm

Günther,

When Harbour is built we can decide if we want C or CPP output files.
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42074
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain

Re: Experiences from convert to 64Bit BCC

Postby byte-one » Thu Mar 31, 2016 5:08 pm

Also with current Harbour in mak:
Code: Select all  Expand view
.prg.cpp:
   $(HARBOUR_EXE) $(HARBOUR_FLAGS) $** -o$@
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria

Re: Experiences from convert to 64Bit BCC

Postby byte-one » Thu Mar 31, 2016 9:23 pm

All Clang compilers use .a as lib- and .o as objectfile. This should be respected in all make-files.
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria

Re: Experiences from convert to 64Bit BCC

Postby byte-one » Fri Apr 01, 2016 5:15 am

You can also use the switch -O2 to enable all (speed)-optimizations from BCC64.exe
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria

Re: Experiences from convert to 64Bit BCC

Postby byte-one » Fri Apr 01, 2016 7:20 am

To own c-files should be added the fwh.h and all constructs "( HDC ) hb_parnl( param )" should now be wrote as "( HDC ) fw_parH( param )" to be compatible.

Antonio this should expanded to HWND and HFONT too!
Regards,
Günther
---------------------------------
office@byte-one.com
User avatar
byte-one
 
Posts: 1048
Joined: Mon Oct 24, 2005 9:54 am
Location: Austria


Return to FiveWin for Harbour/xHarbour

Who is online

Users browsing this forum: No registered users and 88 guests