strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
office-gobmx/icu
History
Kurt Zenker 0ae49dc098 INTEGRATION: CWS icuupgrade (1.7.12); FILE MERGED 
2006/09/21 07:05:05 obo 1.7.12.4: #i60645# update to 3.6
2006/07/07 19:45:30 khong 1.7.12.3: #i60645# change tool util library name
2006/06/22 10:43:46 obo 1.7.12.2: #i60645# deliver icudt34.dll as icudt34l.dll
2006/06/15 16:31:52 khong 1.7.12.1: #i60645# upgrade icu to 3.4.1
2006-12-12 15:02:48 +00:00
..
prj INTEGRATION: CWS icuupgrade (1.7.12); FILE MERGED 2006-12-12 15:02:48 +00:00
icu-3.6.patch INTEGRATION: CWS icuupgrade (1.1.2); FILE ADDED 2006-12-12 14:50:28 +00:00
icuversion.mk INTEGRATION: CWS icuupgrade (1.3.24); FILE MERGED 2006-12-12 14:50:48 +00:00
makefile.mk INTEGRATION: CWS icuupgrade (1.29.8); FILE MERGED 2006-12-12 14:51:25 +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

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.