office-gobmx

History

Jens-Heiner Rechtien c5c13c0be9 CWS-TOOLING: integrate CWS cloph13 2009-09-01 #i104566# also use syslibroot/isysroot for external components 2009-08-28 #i104568# clean up duplicated definitions of OBJCXXFLAGS 2009-08-28 #i104567# add ccache-detection to configure (to skip to objcxx-flags) 2009-08-28 #i104566# use Mac OS X 10.4-SDK to ensure backwards compatibility use MACOSX_DEPLOYMENT_TARGET and sysroot/syslibroot switches ignore "-isysroot /Developer/..." arguments for OOo's cpp		2009-09-16 14:49:32 +00:00
..
prj	CWS-TOOLING: integrate CWS i18n42	2008-10-28 08:56:37 +00:00
createmak.cfg	#i10000# fix for wntmsci10	2009-03-26 09:59:57 +00:00
createmak.pl	CWS-TOOLING: integrate CWS obo36	2009-03-24 11:56:29 +00:00
icu-4.0.patch	CWS-TOOLING: integrate CWS mingwport22	2009-08-26 06:36:38 +00:00
icuversion.mk	CWS-TOOLING: integrate CWS i18n42	2008-10-28 08:56:37 +00:00
makefile.mk	CWS-TOOLING: integrate CWS cloph13	2009-09-16 14:49:32 +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.