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....
thanks for your feedback
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!
Günther,
When Harbour is built we can decide if we want C or CPP output files.
.prg.cpp:
$(HARBOUR_EXE) $(HARBOUR_FLAGS) $** -o$@All Clang compilers use .a as lib- and .o as objectfile. This should be respected in all make-files.
You can also use the switch -O2 to enable all (speed)-optimizations from BCC64.exe
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.