office-gobmx

History

Tor Lillqvist eefc25d1d2 Bin USE_MINGW Its alternative values as used by OOo is irrelevant to us as we don't intend to support building using MinGW on Windows itself. To us, MinGW always means cross-compilation. For us it is enough to look at $(OS)$(COM), and WNTGCC always implies cross-compilation. (OOo on the other hand attempts to support use of the Cygwin gcc with the -mno-cygwin option (which is practically considered an obsolete option), the normal MinGW compiler (but still from Cygwin), but not cros-compilation.)		2011-08-26 20:54:59 +03:00
..
prj
createmak.cfg
createmak.pl
icu-mp.patch
icu4c-4_4_2-wchar_t.patch
icu4c-aix.patch
icu4c-build.patch
icu4c-escapespace.patch
icu4c-rpath.patch
icu4c-strict-c.patch
icu4c-warnings.patch
icu4c.8320.freeserif.crash.patch
icuversion.mk
makefile.mk	Bin USE_MINGW	2011-08-26 20:54:59 +03:00
Readme

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.