2009-09-20 18:12 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl) * harbour/harbour-win-spec * harbour/harbour-wce-spec * harbour/bin/hb-func.sh * harbour/config/global.mk * updated to work with modified base make internals and envvars * do not overload defined by user HB_TOOLS_PREF ! fixed c&p typo in DJGPP cross build HB_TOOLS_PREF Warning: it still needs export HB_BUILD_SHARED=no before creatingRPMs but it should be fixed in base make together with native builds.TODO: we should agree some conditions for alternative system wide cross build installation, like .cfg file name and localization.
It's unclear for me yet the exact purpose we'd like to use HB_TOOLS_PREF for. I see it being used for hbmk scripts, plus dynlib helper script. If we want to take it to the next level IMO it should be renamed to HB_HBPREFIX or HB_BIN_PREFIX and used to prefix all tools. But f.e. hbmk2 has regular cmdline switches to select target platform, so in this case the only reason a prefix would be needed is to differentiate between different *host* builds. (ie. the same hbmk2 linux binary is able to produce win/wce/linux targets) So here the only question is where to put libs/dlls. (f.e. /usr/lib/harbour/win/mingw/, /usr/lib/harbour/wce and /usr/harbour/linux/gcc) In unified Windows installer this is currently solved using postfixes. Here I planned to store different host builds in separate dir, and compared to pre/postfixes it has the disadvantage that they cannot be put in PATH at the same time. pre/postfixes however has the disadvantage that for MS-DOS hosted one we always have to create an exception. Brgds, Viktor _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
