adb5525740
Recognize the arm-linux-androideabi "triplet". (Actually I doubt that is a well-formed triplet at all, what are the Google people smoking?) Allow longer lines in pkgdata.cpp as the compiler command line gets quite long for cross-compilation to Android. Add the proper assembly source file format for Android to pkg_genc.c and use that. Probably a good idea to use --disable-dyload on Android (and iOS). Tweak gcc flags used for Android a bit to work around some Android C header weirdness related to strictness and 64-bit types. |
||
---|---|---|
.. | ||
prj | ||
createmak.cfg | ||
createmak.pl | ||
icu-mp.patch | ||
icu4c-4_4_2-wchar_t.patch | ||
icu4c-aix.patch | ||
icu4c-build.patch | ||
icu4c-escapespace.patch | ||
icu4c-rpath.patch | ||
icu4c-warnings.patch | ||
icu4c.8320.freeserif.crash.patch | ||
icuversion.mk | ||
makefile.mk | ||
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.