7c4f2ec8a7
...by allowing our special @___... tokens anywhere within an install name, so that external modules can configure --prefix=/@___... etc. This removes the need for the special extshl and EXTRPATH=LOADER. Also, a new OUT2BIN_NONE can be used for external modules where the generated libraries need the default EXTRPATH=OOO, but generated executables are only used during the build and such need RPATH=NONE. |
||
---|---|---|
.. | ||
prj | ||
arm-assembler.patch | ||
createmak.cfg | ||
createmak.pl | ||
CVE-2011-4599.patch | ||
icu-mp.patch | ||
icu4c-4_4_2-wchar_t.patch | ||
icu4c-aix.patch | ||
icu4c-android.patch | ||
icu4c-build.patch | ||
icu4c-escapespace.patch | ||
icu4c-rpath.patch | ||
icu4c-strict-c.patch | ||
icu4c-warnings.patch | ||
icu4c.8320.freeserif.crash.patch | ||
icuversion.mk | ||
makefile.mk | ||
README |
Library providing Unicode support, from [http://site.icu-project.org/]. == Makefiles == The procedure of creating and maintaining makefiles.zip The automatically generated makefiles are not necessarily optimal. The build is started from allinone/all directory, and the all.mak file is used to build the entire module through. Each subtarget in this file is going to be made recursively unless there is a switch RECURSE=0. If the switch is available, for each subtarget all its prerequisites should be made earlier than the subtarget itself. Therefore, you should order the ALL target's prerequisites so that they are going to be built in a consistent order. Unfortunately there's no automatic process for it, just prove the prerequisites for each subtarget and push them forward in target's ALL prerequisites list. The changes between generated & optimized all.mak can be seen when comparing the files from v1.5 & v1.6 of makefiles.zip.