1.1 --- a/config/global.in	Sun Jun 17 13:02:21 2007 +0000
     1.2 +++ b/config/global.in	Sun Jun 17 14:51:37 2007 +0000
     1.3 @@ -9,7 +9,7 @@
     1.4  
     1.5  menu "Paths and misc options"
     1.6  
     1.7 -comment "Crosstool behavior"
     1.8 +comment "Crosstool-ng behavior"
     1.9  
    1.10  config EXPERIMENTAL
    1.11      bool
    1.12 @@ -194,6 +194,16 @@
    1.13        Remove the installed documentation (man and info pages).
    1.14        Gains around 8MiB for a uClibc-based, C and C++ compiler.
    1.15  
    1.16 +config INSTALL_DIR_RO
    1.17 +    bool
    1.18 +    prompt "Render the toolchain read-only"
    1.19 +    default n
    1.20 +    help
    1.21 +      Render the directory of the toolchain (and its sub-directories)
    1.22 +      read-only.
    1.23 +      
    1.24 +      Usefull for toolchains destined for production.
    1.25 +
    1.26  comment "Downloading"
    1.27  
    1.28  config FORCE_DOWNLOAD
    1.29 @@ -252,7 +262,7 @@
    1.30      prompt "ERROR"
    1.31      help
    1.32        The build will be silent.
    1.33 -      Only if there is an error will you see a mesage.
    1.34 +      Only if there is an error will you see a message.
    1.35  
    1.36  config LOG_WARN
    1.37      bool
    1.38 @@ -297,17 +307,19 @@
    1.39  
    1.40  config LOG_SEE_TOOLS_WARN
    1.41      bool
    1.42 -    prompt "Warnings from the tool builds as CT warnings"
    1.43 +    prompt "Warnings from the tools' builds"
    1.44      default n
    1.45      depends on ! LOG_ERROR
    1.46      help
    1.47 -      Treat warnings fron the different tools as crosstool warnings.
    1.48 +      Treat warnings from the different tools as crosstool-ng warnings.
    1.49        If you say 'y' here, then those warnings will be prefixed with
    1.50        '[WARN ]' instead of the default '[ALL  ]'.
    1.51  
    1.52        You can safely say 'n' here. Those warnings will anyway be
    1.53        recorded in the log file (provided you configured one).
    1.54  
    1.55 +      Tools error will always be logged as crosstool-ng errors.
    1.56 +
    1.57  config LOG_PROGRESS_BAR
    1.58      bool
    1.59      prompt "Progress bar"
    1.60 @@ -330,19 +342,20 @@
    1.61      default y
    1.62      help
    1.63        Save *full* logs to a file. Even log levels you didn't specify above
    1.64 -      will be available in this file.
    1.65 +      will be available in this file. The log file will be named build.log
    1.66 +      and stored in the toolchain prefix dir (set above).
    1.67  
    1.68        As a bonus, there is a script in tools/extractConfig.sh that is able
    1.69        to extract the configuration of crosstool-NG from the log file.
    1.70  
    1.71        Definitely, say Y.
    1.72  
    1.73 -config LOG_FILE
    1.74 -    string
    1.75 -    prompt "Log file"
    1.76 -    default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
    1.77 +config LOG_FILE_COMPRESS
    1.78 +    bool
    1.79 +    prompt "Compress the log file"
    1.80 +    default n
    1.81      depends on LOG_TO_FILE
    1.82      help
    1.83 -      File name into which to put logs.
    1.84 +      Compress the log file once the toolchain is successfully built.
    1.85  
    1.86  endmenu