Hi Przemek, Is it safe to do this, then? hbmk2 -q0 -shared -ohbrun-dll hbrun.hbm -lhbcplr -lhbpp -lhbcommon
If not, how to resolve it? Brgds, Viktor On Wed, Apr 8, 2009 at 5:46 AM, Przemyslaw Czerpak <dru...@acn.waw.pl>wrote: > On Wed, 08 Apr 2009, Szak�ts Viktor wrote: > > Hi, > > > Until then, you can add static libs to resolve the missing symbols: > > hbmk2 my.prg -lhbwin -lxhb -shared -lhbvm -lhbrtl -lhbcommon -lhbmacro > > It's very bad idea. In windows .dll is self contain binary so in such > way you will create final executable with to independent copies of HVM > and some other functions. The binaries will be created but final > results unpredictable. F.e. some functions will operate on HVM stack > inside harbour.dll and some others on HVM stack linked with final > binaries. What will happen you can try to guess if you carefully study > map file and all function bindings in final binaries but for sure it > will not be correct behavior. > _NEVER_ make anything like that. When harbour.dll is used no other > libraries which are part for harbour.dll should be used to link > the program. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
