> This is probably the _REAL_ cause. > > I have checked, if not otherwise nullified, even if -st flag is > sent to hbMK2, it always compiles C code as : > > bcc32.exe -c -q -tWM -d -6 -O2 -OS -Ov -Oi -Oc -w -Q -w-sig- > -nE:\dev_hbmk\xharbour\obj\cacherdd -IC:\xharbour\include > -ID:\Projects\CacheRDD\Include E:\dev_hbmk\xharbour\obj\cacherdd\CacheRDD.c > > and in link script "cw32mt.lib" is visible. > > So I need to wait till Viktor's response.
So as I asked before, can you show what are the compiler/linker command lines for a successful build when using native xhb build tools? Then I need to see test results with an xhb build which is guaranteed to be built properly. After that I'll probably need more input from experiences xhb users, as to which bcc options to use and when. To me xhb MT/ST support and build method/settings look very confusing. On the hbmk2 level it will probably come down to controlling -tWM compiler option and CRTL lib in ilink command. Easy to make the change once we know the rules. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
