Ignore:
Timestamp:
Mar 25, 2010, 12:05:40 AM (11 years ago)
Author:
dmik
Message:

branches/kmk: env.cmd: Added an easy way to activate the debug build and some more documentation.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/kmk/README.DEV

    r314 r317  
    1818    is recommended to download a ready-to-use GCC 4.2.2 distribution from here:
    1919
    20       ftp://ftp.netlabs.org/pub/qt4/gcc-4_4_2-complete-20091205.zip
     20      ftp://ftp.netlabs.org/pub/qt4/tools/gcc-4_4_2-complete-20091205.zip
    2121
    2222    Follow the installation instructions contained in the README file inside
     
    5555  ftp://ftp.netlabs.org/pub/qt4/tools/se10.zip
    5656
     57
     58
     59USEFUL KBUILD VARIABLES
     60
     61These are the frequently used variables that change the Lucide build or
     62behavior. You may set them in the OS/2 environment or put to your
     63"LocalConfig.kmk" or pass to "kmk" as command line arguments in the form of
     64"VARIABLE=VALUE".
     65
     66  * BUILD_TYPE
     67
     68    Build type. May be set to "release" (default) or "debug".
     69
     70    Note that you may also pass "debug" or "release" as the first argument to
     71    the "env.cmd" script to set the build type to "debug".
     72
     73    Hint: If you use "se.cmd", you may pass arguments to "env.cmd" and start
     74    "kmk" in one step, like that: "se @(debug) kmk".
     75
     76  * KBUILD_VERBOSE
     77
     78    Level of kBuild verbosity, 1 to 3 (default is nothing which means almost
     79    quiet). The highest level will make kBuild print every command it executes
     80    which is useful when something does not work like you want.
     81
Note: See TracChangeset for help on using the changeset viewer.