Changes between Version 2 and Version 3 of user-configure


Ignore:
Timestamp:
May 26, 2006 4:18:38 PM (14 years ago)
Author:
andreasw
Comment:

config.site file - finished first draft

Legend:

Unmodified
Added
Removed
Modified
  • user-configure

    v2 v3  
    1313}}}
    1414
    15 This picks default settings for compilers and compiler options.  You can change some aspects of the configuration by providing arguments to the configuration script, as described next.
     15This picks default settings for compilers and compiler options.  You can change some aspects of the configuration by providing arguments to the configuration script, as described below.
     16
     17If the configuration is successful, the {{{configure}}} script usually prints a message indicating this.  If the configuration fails, the output on the screen, or the more detailed output in the {{{config.log}}} in the same directory might help to find the cause.  If you look at the {{{config.log}}} file, you should go to the bottom of this file and page up, until you see the error message; at the end of the file {{{configure}}} still outputs the results of the tests, even in case of failure.
     18
     19If you are not able to fix the problem and want to contact the maintainers, you should submit a bug ticket at the corresponding Trac page and attach the {{{config.log}}} file.
    1620
    1721== Giving Options to the {{{configure}}} script ==
     
    8589== Specifying Options in a {{{config.site}}} File ==
    8690
     91Setting all configuration arguments in the command line for {{{configure}}} can be somewhat inconvenient.  You can alternatively specify your choices in a file that is automatically read when {{{configure}}} is run.
     92
     93The name of this file is {{{config.site}}}.  The {{{configure}}} script looks for it in the {{{share}}} subdirectory of the installation directory (i.e., what you speficy with the {{{--prefix}}} argument, or by default in the {{{share}}} subdirectory of where you run {{{configure}}}).  You can specify a different location and name by setting the environment variable {{{CONFIG_SITE}}} to the full path to your {{{config.site}}} file, including the file name itself.
     94
     95The {{{config.site}}} file is a shell script (for {{{bin/sh}}}) and needs to follow the shell's syntax.  It is used to set values of shell variables that are internally used by the {{{configure}}} script.  In case of variable arguments (such as {{{CC}}}), the name that should be used in {{{config.site}}} is identical to the name that could be specified in the command line.  For {{{--enable-...}}}-type arguments, the corresponding {{{config.site}}} shell variable is {{{enable_...}}} with the dashes replaced by underscore; to specify that the features is to be used, set this variable to {{{yes}}}, and to disable it, set it to {{{no}}}.  For {{{--with-...}}}-type arguments use the variable name {{{with_...}}}, again with dashes replaced by underscores, and set it to the chosen value.  If no value is required, set it to {{{yes}}}, and to minic a {{{--without...}}} option, set the corresponding {{{with_...}}} variable to {{{no}}}.
     96
     97An example {{{config.site}}} file can be found in the {{{BuildTools/config.site}}} directory.