office-gobmx/icu
Tor Lillqvist adb5525740 Initial attempt at Android cross-compilation support
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.
2011-06-11 17:50:36 +03:00
..
prj Drop %_EXT% which was always empty 2011-06-03 13:27:35 +03:00
createmak.cfg Don't use pointless and obsolete switches when building ICU 2011-01-22 03:42:25 +02:00
createmak.pl changefileheader2: #i109125#: change source file copyright notice from Sun Microsystems to Oracle; remove CVS style keywords (RCSfile, Revision) 2010-02-12 15:01:35 +01:00
icu-mp.patch ause124: #i107097#: add dependencies for directory creation 2010-07-21 13:12:39 +02:00
icu4c-4_4_2-wchar_t.patch Make icu 4.4.2 build on Linux 2011-03-15 11:21:43 +01:00
icu4c-aix.patch fix aix patch 2011-03-11 10:01:47 +00:00
icu4c-build.patch Initial attempt at Android cross-compilation support 2011-06-11 17:50:36 +03:00
icu4c-escapespace.patch escape spaces in compiler name 2011-03-15 21:44:17 +00:00
icu4c-rpath.patch icu-4.2.1-rpath.diff: pass $ORIGIN correctly to icu RPATH 2011-03-29 17:59:06 +02:00
icu4c-warnings.patch WaE: silence new icu warnings 2011-03-11 14:43:36 +00:00
icu4c.8320.freeserif.crash.patch restore build of build patch that seem to still make sense 2011-03-11 09:03:27 +00:00
icuversion.mk Downgrade icu to 4.4.2 2011-03-15 10:35:24 +01:00
makefile.mk Initial attempt at Android cross-compilation support 2011-06-11 17:50:36 +03:00
Readme INTEGRATION: CWS icuopt (1.1.2); FILE ADDED 2005-05-06 08:23:32 +00:00

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.