Luis: > Ok.... by adding ace32 to contrib\rdd_ads\makefile.bc > it now compiled fine. > > But.... isn't it just more work to update ace32.c each time > ADS makes a new release.
As far as there is no developers updating/adding the new functionalities appears in new version, there should be no update required per status-quo. If a new functionality is to be brought into the codes, certainly the ace32.c should be modified accordingly, but this is a minor job. IMO, this is common in programming. > It would seem to me it way simpler to just do the implib > thing to build ace32.lib. You are right if you work only with _ONE_ version. But if you have to switch to another/previous version than you'll have to re-do the import-lib and recompile, right? With the current configuration, there is no need to do that. All you need to do is simply replace the DLL with the version you want to work with. No recompile or import-lib is needed. FYI, the current construct makes us possible to work with version 2.6 through 9.0 without recompiling and without care about correct version of ACE32.LIB. > Maybe I'm missing something here. You are not. -- 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 xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
