office-gobmx/icu
2011-02-08 19:44:39 +01:00
..
prj
createmak.cfg ause117: #i110339# avoid collisions of inline files 2010-03-23 18:19:02 +01: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_0_1-src.patch
icuversion.mk locales34: #i112240# for system icu >=4.4 add Close_Parenthesis to $CL Close_Punctuation; patch from <cmc> 2011-01-27 23:56:24 +01:00
makefile.mk mingwport33: i#116329: MinGW port enhancement: configurable libstdc++ name 2011-01-06 21:56:21 +09: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.