Changeset 9165 for trunk/make/setup.mak


Ignore:
Timestamp:
Aug 29, 2002, 12:01:46 PM (23 years ago)
Author:
bird
Message:

Added new tools. Restructured tools. More options. Fixes.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/make/setup.mak

    r9150 r9165  
    1 # $Id: setup.mak,v 1.15 2002-08-28 03:47:09 bird Exp $
     1# $Id: setup.mak,v 1.16 2002-08-29 10:01:40 bird Exp $
    22
    33#
     
    130130PATH_INCLUDES   = $(PATH_ROOT)\include\win;.;$(PATH_ROOT)\include
    131131# Where the temporary files goes.
    132 PATH_OBJ        = $(PATH_ROOT)\obj\$(SHT_TRGPLTFRM)$(SHT_BLDMD)$(SHT_BLDENV)
     132PATH_OBJ        = $(PATH_ROOT)\obj\$(SHT_TRGPLTFRM)$(SHT_BLDMD)$(SHT_BLDENV:-=_)
    133133# Where the libraries goes.
    134134PATH_LIB        = $(PATH_ROOT)\lib\$(BUILD_MODE)
     
    206206MAKE_INCLUDE_PROCESS    = $(PATH_MAKE)\process.mak
    207207
     208# -----------------------------------------------------------------------------
     209# Build the environments variables
     210# -----------------------------------------------------------------------------
     211
     212# In the makefiles you're allowed to use the BUILD_ENVS_PRE,
     213# BUILD_ENV_FORCE, BUILD_ENVS_POST variables to make private changes to the
     214# environment. These are combined with the two base ones as follows:
     215#   $(BUILD_ENVS_BASE_PRE) $(BUILD_ENVS_PRE) $(ENV_ENVS) $(BUILD_ENVS_BASE_POST) $(BUILD_ENVS_POST)
     216#
     217# BUILD_ENV_FORCE is used for changing the base compiler. Do *NOT* use
     218# BUILD_ENV for that! BUILD_ENV_FORCE isn't used directly but in the setup
     219# string above, but ENV_ENVS from the setup.[w]xyz.mk setup file is used.
     220#
     221
     222# These strings are passed on to the BuildEnv.cmd script to setup the correct
     223# shell environment.
     224# TODO   Should these be overridable by setup.[w]xyz.mak ? (kso)
     225BUILD_ENVS_BASE_POST    = toolkit40
     226BUILD_ENVS_BASE_POST_16 =
     227BUILD_ENVS_BASE_PRE     = buildsetup emx cvs
     228BUILD_ENVS_BASE_PRE_16  = buildsetup emx cvs toolkit40 ddkbase
     229
    208230
    209231# -----------------------------------------------------------------------------
     
    279301#
    280302
    281 # -----------------------------------------------------------------------------
    282 # Build the environments
    283 # -----------------------------------------------------------------------------
    284 
    285 # In the makefiles you're allowed to use the BUILD_ENVS_PRE,
    286 # BUILD_ENV_FORCE, BUILD_ENVS_POST variables to make private changes to the
    287 # environment. These are combined with the two base ones as follows:
    288 #   $(BUILD_ENVS_BASE_PRE) $(BUILD_ENVS_PRE) $(ENV_ENVS) $(BUILD_ENVS_BASE_POST) $(BUILD_ENVS_POST)
    289 #
    290 # BUILD_ENV_FORCE is used for changing the base compiler. Do *NOT* use
    291 # BUILD_ENV for that! BUILD_ENV_FORCE isn't used directly but in the setup
    292 # string above, but ENV_ENVS from the setup.[w]xyz.mk setup file is used.
    293 #
    294 
    295 # These strings are passed on to the BuildEnv.cmd script to setup the correct
    296 # shell environment.
    297 # TODO   Should these be overridable by setup.[w]xyz.mak ? (kso)
    298 
    299 BUILD_ENVS_BASE_POST    = toolkit40
    300 BUILD_ENVS_BASE_POST_16 =
    301 BUILD_ENVS_BASE_PRE     = buildsetup emx cvs
    302 BUILD_ENVS_BASE_PRE_16  = buildsetup emx cvs toolkit40 ddkbase
    303 
    304 #
     303
     304# -----------------------------------------------------------------------------
    305305# Forwarding processing.
    306 #
     306# -----------------------------------------------------------------------------
    307307!if $(BUILD_FORWARDING)
    308308
Note: See TracChangeset for help on using the changeset viewer.