Changeset 251


Ignore:
Timestamp:
Mar 7, 2003, 5:18:40 PM (22 years ago)
Author:
umoeller
Message:

Misc fixes.

Location:
trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/makefile

    r8 r251  
    1313all:
    1414    @cd src\helpers
    15     nmake -nologo "MAINMAKERUNNING=YES"
     15    nmake -nologo
    1616    @cd ..\..
    1717
     18dep:
     19    cd src\helpers
     20    nmake -nologo dep "SUBTARGET=dep" "RUNDEPONLY=1"
     21    cd ..\..
    1822
  • trunk/readme.txt

    r136 r251  
    154154    parameters to the makefiles.
    155155
    156     The most important environment variable is PROJECT_BASE_DIR.
    157     This should point to the root directory of your own project.
    158     In this directory, src\helpers\makefile expects a file called
    159     "setup.in" which sets up more environment variables. You can
    160     take the one from the XWPHelpers makefile as a template.
    161 
    162     Here's an example: Say you have a CVS root directory of
    163     "C:\cvs" on your system. The XWPHelpers reside in
    164     "C:\cvs\xwphelpers". Your own project resides in
    165     "C:\cvs\myproject" (plus subdirectories). So set
    166     PROJECT_BASE_DIR to "C:\cvs\myproject" and put setup.in
    167     in that directory.
    168 
    169     Note that the XWPHelpers also expect a "setup.h" header
    170     file to be somewhere on your INCLUDE path. See remarks
    171     below.
    172 
    173     See the top of src\helpers\makefile for additional variables.
     156    --  The most important environment variable is PROJECT_BASE_DIR.
     157        This should point to the root directory of your own project.
     158
     159    --  In the "make" subdirectory of that directory, the helpers
     160        makefiles expect a file called "setup.in" which sets up more
     161        environment variables. You can take the ones from XWorkplace
     162        or WarpIN as a template. Those setup.in files in turn expect
     163        a config.in in PROJECT_BASE_DIR itself, but that is no
     164        precondition required by the helpers makefiles themselves.
     165
     166        Here's an example: Say you have a CVS root directory of
     167        "C:\cvs" on your system. The XWPHelpers reside in
     168        "C:\cvs\xwphelpers". Your own project resides in
     169        "C:\cvs\myproject" (plus subdirectories). So set
     170        PROJECT_BASE_DIR to "C:\cvs\myproject", create
     171        "C:\cvs\myproject\make", and put setup.in in there.
     172
     173    --  OUTPUTDIR_HELPERS must point to the directory where the
     174        output .obj and .lib files should be created.
     175
     176    --  Note that the XWPHelpers also expect a "setup.h" header
     177        file to be somewhere on your INCLUDE path. See remarks
     178        below.
    174179
    175180    Of course, nothing stops you from writing your own makefile
     
    180185
    181186        @cd xxx\src\helpers
    182         nmake -nologo "PROJECT_BASE_DIR=C:\myproject" "MAINMAKERUNNING=YES"
     187        nmake -nologo "PROJECT_BASE_DIR=C:\myproject" "OUTPUTDIR_HELPERS=C:\myproject\bin" "MAINMAKERUNNING=YES"
    183188        @cd olddir
    184189
Note: See TracChangeset for help on using the changeset viewer.