1.1 --- a/config/global/paths.in	Thu Apr 17 20:26:25 2008 +0000
     1.2 +++ b/config/global/paths.in	Tue Jun 24 16:19:45 2008 +0000
     1.3 @@ -19,6 +19,27 @@
     1.4        If you say 'y' here, new downloaded tarballs will be saved in the
     1.5        directory you entered above.
     1.6  
     1.7 +config WORK_DIR
     1.8 +    string
     1.9 +    prompt "Working directory"
    1.10 +    default "${CT_TOP_DIR}/targets"
    1.11 +    help
    1.12 +      Set this to the directory where all build actions will be done.
    1.13 +      
    1.14 +      The default is "${CT_TOP_DIR}/targets", and leaving this option
    1.15 +      empty will also use the default.
    1.16 +      
    1.17 +      You should not need to change that, except in one very peculiar
    1.18 +      setup:
    1.19 +       - your crosstool-NG source directory is on the network
    1.20 +       - you configured crosstool-NG with --local
    1.21 +      This kind of setup is a pain, as any action involving source file
    1.22 +      access would have to go through the wire. In this case, you should
    1.23 +      set CT_WORK_DIR to point to a path local to your machine, to avoid
    1.24 +      any network overhead.
    1.25 +      
    1.26 +      Do *NOT* change it if you don't know better.
    1.27 +
    1.28  config PREFIX_DIR
    1.29      string
    1.30      prompt "Prefix directory"
    1.31 @@ -31,7 +52,7 @@
    1.32  #    prompt "Install directory"
    1.33      default "${CT_PREFIX_DIR}"
    1.34  #    help
    1.35 -#      This is the path the target will be installed into.
    1.36 +#      This is the path the toolchain will be installed into.
    1.37  #      
    1.38  #      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
    1.39  #      you can't write there, you can install somewhere else and have a third