diff options
| author | Josh Heidenreich <josh.sickmate@gmail.com> | 2012-02-09 18:21:10 +1030 |
|---|---|---|
| committer | Petr Mladek <pmladek@suse.cz> | 2012-02-09 18:23:49 +0100 |
| commit | b469be0723812746dc22fb0a2de69499488f5a35 (patch) | |
| tree | 90216be8bc9420bc3be5793acbb25e8fbefa7727 /icu | |
| parent | 295cc6c5bce83c48aa92254687b2251c09115e67 (diff) | |
Added and improved READMEs for modules in libs-extern-sys
Diffstat (limited to 'icu')
| -rw-r--r-- | icu/README | 15 | ||||
| -rw-r--r-- | icu/Readme | 4 |
2 files changed, 15 insertions, 4 deletions
diff --git a/icu/README b/icu/README new file mode 100644 index 000000000000..2864775c1345 --- /dev/null +++ b/icu/README @@ -0,0 +1,15 @@ +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. diff --git a/icu/Readme b/icu/Readme deleted file mode 100644 index 23c2bfdc5e7b..000000000000 --- a/icu/Readme +++ /dev/null @@ -1,4 +0,0 @@ -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. |