> > > Now only this warning remains: > > Warning! W1171: Locally defined symbol hb_stricmp is imported. > > (why only this one, I don't know. It's caused by '-lhbcplr -lhbpp > > -lhbcommon' parameters when building hbrun-dll, hbmk2-dll) > > Not only this one. In general we do not revert export/import flag > at all what may cause some bad results. As I can see for > hb_vmSetLinkedMain() and hb_gtSetDefault() you simply removed > import attributes from some builds to pacify warnings. It should > be done in different way. We need macro to define HB_EXPORT as HB_IMPORT. > Probably -DHB_EXPORT=HB_IMPORT is enough but I haven't tested. > The fact that the harbour.dll works suggests that some C compilers can > resolved wrong definitions in some hidden way at least using import > library. Maybe with valid flags some of them will be able to use > harbour.dll directly.
I'm afraid I cannot oversee this for full Harbour, I'd appreciate if someone could help fixing it. > BTW in Linux shared builds are broken in hbmk2 and still -llibharbour > is used instead of -lharbour. -llibharbour is used since the beginning. The problem was arch/comp lib dir autodetection. After today's fix it should work again. Brgdsm Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
