Name Date Size #Lines LOC

..--

prj/H--4235

ReadmeH A D16-Aug-2011887 53

createmak.cfgH A D14-Jun-202414.5 KiB492358

createmak.plH A D14-Jun-202437.8 KiB1,153894

icu-darwin.patchH A D27-Oct-2024754 1512

icu-format-security.patchH A D01-Nov-2024528 1312

icu-mp.patchH A D16-Aug-20111.3 KiB2523

icu-win-icutu-dll-version.patchH A D14-Jun-20241.4 KiB4140

icu-win-layout.patchH A D14-Jun-2024791 1211

icu-win-layoutex.patchH A D18-Sep-2016658 1110

icu4c-4_0_1-src.patchH A D23-Apr-201313.5 KiB320285

icu4c-4_2_1-src.patchH A D27-Oct-202410.6 KiB231203

icuversion.mkH A D14-Jun-20241,008 303

makefile.mkH A D14-Jun-20249.9 KiB284160

Readme

1This file describes the procedure of creating and maintaining makefiles.zip
2# Obo's part
3
4    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.
5