office-gobmx/icu
Vladimir Glazounov 5bfe436c1f INTEGRATION: CWS mingwport07 (1.7.10); FILE MERGED
2007/10/16 10:13:03 vg 1.7.10.1: #i82653# MinGW port efforts
2007-10-26 10:31:43 +00:00
..
prj INTEGRATION: CWS mingwport03 (1.3.170); FILE MERGED 2007-03-26 12:41:52 +00:00
icu-3.6.patch INTEGRATION: CWS mingwport07 (1.7.10); FILE MERGED 2007-10-26 10:31:43 +00:00
icuversion.mk INTEGRATION: CWS icuupgrade (1.3.24); FILE MERGED 2006-12-12 14:50:48 +00:00
makefile.mk INTEGRATION: CWS configure21 (1.35.4); FILE MERGED 2007-07-31 12:04:47 +00:00
makefiles.zip INTEGRATION: CWS icuupgrade (1.7.32); FILE MERGED 2006-12-12 14:52:15 +00: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.