diff options
author | kennyballou <kballou@onyx.boisestate.edu> | 2013-01-21 17:25:35 -0700 |
---|---|---|
committer | kennyballou <kballou@onyx.boisestate.edu> | 2013-01-21 17:25:35 -0700 |
commit | 66c9d714bffe76ccb8434d1dfac9298967540ef3 (patch) | |
tree | 960402c833367effd44173deb39d22dc8c824ef9 /docs/source/xenant.rst | |
parent | d1771d0d435c71217f698331fac2ac03826b57da (diff) | |
download | xnt-66c9d714bffe76ccb8434d1dfac9298967540ef3.tar.gz xnt-66c9d714bffe76ccb8434d1dfac9298967540ef3.tar.xz |
Update documentation: Add Parameter passing
Restructure documentation to better suite the parameter passing
section(s); add two sections: how to invoke xnt to pass parameters,
and how to add/use them in the build file
Diffstat (limited to 'docs/source/xenant.rst')
-rw-r--r-- | docs/source/xenant.rst | 89 |
1 files changed, 89 insertions, 0 deletions
diff --git a/docs/source/xenant.rst b/docs/source/xenant.rst new file mode 100644 index 0000000..86a26da --- /dev/null +++ b/docs/source/xenant.rst @@ -0,0 +1,89 @@ +Running Xnt +=========== + +Invoking Xnt from the command line is very simple and very similar to how other +build tools are invoked (this was intentional). + +.. _defaultUse: + +Default Use +----------- + +The most simplistic use of Xnt is as follows:: + + $ xnt + +This will attempt to invoke the `default` target in the current directory's +`build.py`. + +.. _invokeTarget: + +Invoke a Target +--------------- + +To invoke a particular target, use:: + + $ xnt {target} + +Where the value of `{target}` is dependent on your particular `build.py` file. + +.. _specialTargets: + +Special Targets +--------------- + +"Special" targets (for lack of a better name) are targets that do not exist in +the build script, but rather are a part of Xnt. + +Thus far, I have only defined one "special" target, ``list-targets`` (I don't +think this name is going to change again ...). + +* ``list-targets`` does exactly what the name should suggest: it prints a list + of the targets found in the current directory's `build.py` script, along with + any docstrings that may be defined with them. + +Usage:: + + $ xnt list-targets + +.. _xntOptions: + +Options +------- + +Xnt also has a few "options" that may be provided along with a regular targets. + +Usage:: + + $ xnt [options] [target] + +Where options can be any and all of the following (unless otherwise specified): + +* ``-v``: add verbose output to the execution of Xnt + +* ``--version``: Print the version of Xnt and exit + +* ``--usage``: Print version, license, usage information and quit. [I've + debatted between putting this as a special target and leaving it as an + option.. not sure which is better...] + +.. _xntPropertiesParameters: + +Properties and Parameter Passing +-------------------------------- + +Xnt now has the ability to accept command line parameters and forward them to +your `build.py` file. This can be useful for a number of reasons: flipping +debug flags, deployment flags and the like or whatever else you can imagine. + +The general semantic for passing the parameters is as follows:: + + $ xnt [-D{name}={value}]+ [options] [target] + +*Notice:* the `-D` is used to distinguish values to be passed to the `build` +file from regular options. You may specify as many parameters as you like and +there is no other real ordering required to be parsed correctly. Just know, +spaces are used to delimit arguments; if your passed value *must* have a space, +remember to quote it. + +Please see :ref:`buildProperties` to see how this works on the `build.py` side. |