office-gobmx/icu
2011-11-21 18:21:49 +02:00
..
prj Use --with-library-suffix=lo for Android to avoid clash with system ICU 2011-11-21 15:48:53 +02:00
createmak.cfg
createmak.pl
icu-mp.patch
icu4c-4_4_2-wchar_t.patch
icu4c-aix.patch
icu4c-android.patch Don't use any major version soname suffix for Android 2011-11-21 01:51:18 +02:00
icu4c-build.patch Don't consider newer Apple compilers having "universal" byte order 2011-09-28 11:41:17 +03:00
icu4c-escapespace.patch
icu4c-rpath.patch
icu4c-strict-c.patch
icu4c-warnings.patch
icu4c.8320.freeserif.crash.patch
icuversion.mk
makefile.mk Use -fno-omit-frame-pointer for Android (no idea if essential) 2011-11-21 18:21:49 +02:00
Readme

This file describes the procedure of creating and maintaining makefiles.zip
# Obo's part

    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.