Changes between Version 1 and Version 2 of Documentation


Ignore:
Timestamp:
Nov 23, 2006, 5:02:32 PM (17 years ago)
Author:
bird
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation

    v1 v2  
    1212 1. [wiki:kmk kmk] will start at the default goal ({{{all_recursive}}}) and resolve all its prerequisites.
    1313 1. This will cause the list of passes in {{{DEFAULT_PASSES}}} to be iterated, recusing into subdirectories if configured to do so for each pass.
     14
     15
     16= The Target Lists =
     17
     18[wiki:kBuild kBuild] will by default pick up and process the following target lists:
     19 1. {{{BLDPROGS}}} - build programs, e.g. programs that will be used later in the build process and will run on the build platform. Will by default be compiled with the {{{BUILD_PLATFORM}}} as target.
     20 1. {{{LIBRARIES}}} and {{{IMPORT_LIBS}}} - object libraries.
     21 1. {{{DLLS}}} - dynamic link libraries and shared objects.
     22 1. {{{PROGRAMS}}} - program binaries.
     23 1. {{{SYSMODS}}} - system modules, kernel extentions, device drivers, etc.
     24 1. {{{OTHERS}}} - user defined targets.
     25 1. {{{INSTALLS}}} - installation targets. This can be excluded from the default pass by adding {{{DEFAULT_PASSES := $(filter-out INSTALLS,$(DEFAULT_PASSES))}}} to the relevant {{{Config.kmk}}}.
     26 1. {{{PACKING}}} - the packing goals. These are the prerequisties for the {{{packing}}} pass.
     27
     28TODO: More details.
     29
     30= The Target Properties =
     31
     32Each target has a number of properties which [wiki:kBuild kBuild] will look for. Some of these properties will come from the '''template''' if used, others will be picked up from the relevant '''tool''' and '''sdks'''. Which properties [wiki:kBuild kBuild] looks for depends on which target list the target was picked up in.