IMO not at all. I'd hate to fiddle with dlls (mean put in path, copy along with exe, handle different version in the path, or the other dir I'd like to copy the exe to, etc) when using these tools. For these tools it won't even save disk space as just the two dlls are 5.1MB (with MSVC), while all standalone tools are altogether about the same size. So what would be the point? (besides making smaller binary distributions, but our package is quite slim anyway)
Just some more notes: non-GNU make MSVC/BCC builds _do_ already provide hbrun-dll.exe and hbtest-dll.exe for those who prefer them. GNU-make MSVC/BCC doesn't even have .dll support yet. Linux distros also use it by default. So I'm not sure which platform have you meant. Brgds, Viktor On Sun, Feb 22, 2009 at 8:32 AM, Lorenzo Fiorini <[email protected]>wrote: > Is there any reason? > > Wouldn't be better to have them linked against harbour shared lib? > > best regards, > Lorenzo > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
