On Tue, 18 Aug 2009, Szak�ts Viktor wrote: >> We do not use autoconf so we have to guess what is available >> on given platform. It creates potential problems in portability, >> i.e. to older systems. I guess that current Harbour cannot be used >> with older MacOSX or Linux builds. Now I'm trying to cover all >> extended functions usage by HB_HAS_* or HB_USE_* macros. >> In the future I plan to group them in one header file which can >> be easy edited by user and/or overloaded (redefined) by autoconf. >> >> I do not have to even know the system name. Clean configuration >> should work with SCO, UNIXWARE and other *nixes not explicitly >> supported by us. Probably we will have to add generic POSIX/UNIX >> platform support to our .mk files. > > I agree with these. As for autoconf, if it can be used as a simple > tool to generate such config header as a pre-make step it can be nice, > but unfortunately autoconf is a *nix only tool, so it will be again > something which will have to be rewritten for non-*nix platforms, > and/or we will have to reintroduce parallel systems (*) for the same > thing for different platforms. I've yet to see what is the "magic" > of autoconf, but if possible I'd try to go in a direction which > is portable (like some .mk detection logic if it's possible to do).
I want to add autoconf support optionally. I'll add empty include/hbaconf.h and include/hbconf.h which will #include hbaconf.h and hbsetup.h and then try to set HB_HAS_* macros using available information. So far everything will work as in current builds but if autoconf is available then it can be used to overwrite empty include/hbaconf.h with settings tuned for given platform. That's all. Then support for even very old OS-es will be only matter of some new rules/macros. We do not have to add explicit support support for different configuration and/or cross compilations but we need an easy way to create native binaries. If necessary we can also generate .mk file with some platform dependent settings hard to detect using pure GNU make code, i.e. is it necessary to use PIC switches and which ones? best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
