Hi, I have followed the thread regarding problems on miss-matched among ace32.lib and ace32.dll. IMO, the elegant solution is not to create ace32.lib out of ace32.dll but to create ace32.lib ourselves, independent of ace32.dll. This way will guarantee us that each C Compiler will have its own version of ace32.lib. If I am not mistaken, there seems to be efforts to "import-lib" during creation of [x]Harbour. That's bad, IMO, because it only covers certain C compilers ie. BCC/MSVC. What about people using DMC, Watcom or any other compilers?
Creating ace32.lib ourselves will guarantee that no missmatch will happen. I have created a raw ace32.lib which has been tested with version 6.xx, 7.xx, 8.10 and 9.0. One single ace32.lib for those version. It seems that version 5.xx has different architecture(?) so the local server failed to initialize. I need to fine tune a bit and will upload when I think it is ready. FYI, when running tests/ads.prg (appending 200,000 recs and indexing), the overhead is very minimal in fraction of a second so it can be disregarded. -- Andi ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ xHarbour-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xharbour-developers
