GNU AutoGen - The Automated Program Generator: 5.26 presetting/configuring autogen

[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

## 5.26 presetting/configuring autogen

Any option that is not marked as not presettable (see section no preset) may be preset by loading values from configuration ("rc" or "ini") files, and values from environment variables named `AUTOGEN` and `AUTOGEN_<OPTION_NAME>`. “`<OPTION_NAME>`” must be one of the options listed above in upper case and segmented with underscores. The `AUTOGEN` variable will be tokenized and parsed like the command line. The remaining variables are tested for existence and their values are treated like option arguments.

Configuration files may be in a wide variety of formats. The basic format is an option name followed by a value (argument) on the same line. Values may be separated from the option name with a colon, equal sign or simply white space. Values may be continued across multiple lines by escaping the newline with a backslash.

Multiple programs may also share the same initialization file. Common options are collected at the top, followed by program specific segments. The segments are separated by lines like:

    [AUTOGEN]

or by

    <?program autogen>

Do not mix these within one configuration file.

Compound values and carefully constructed string values may also be specified using XML syntax:

    <option-name>
       <sub-opt>...&lt;...&gt;...</sub-opt>
    </option-name>

yielding an `option-name.sub-opt` string value of

    "...<...>..."

`Autogen` does not track suboptions. You simply note that it is a hierarchicly valued option. `libopts` does provide a means for searching the associated name/value pair list (see section optionFindValue).

[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

This document was generated by Bruce Korb on March 7, 2011 using texi2html 1.82.