Toninho: > Brian, ...I agree with Ron, but I have one doubt about: > >ADS_REQUIRE_VERSION issue; Viktor has replaced it with a better > >#define as part of his "auto-detecting" ...
> I, for example: have ADS 9.0 installed in my machine for tests > pourposes, but I always compile RDDADS with ADS_REQUIRE_VERSION=7 > because all my custommers have ADS 7. So IMO autodetec is not a good > idea. Actually I believe this is a better solution. (I'll post more details in a moment). The new system allows you to set up your environment to explicitly *build* for version 7, without influence from having v9 also on your machine. In your case, you would want to have one ads\acesdk7 folder for that build, and another ads\acesdk9 folder for whenever you'll want to build for newer features. In my case, I periodically need to go back as far as v6 for debugging older releases of my app, often v7, now v8, and of course I need to update to v9 and start using some of the new features. There is pretty ugly logic controlling how the correct ace32.lib is found for each build. With the new system, a #define lets you specify exactly which version you want to build. And new users of rddads should have a much easier time of getting started. -- Brian Hays ------------------------------------------------------------------------- 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
