1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/config/paths.in	Thu Apr 17 20:02:07 2008 +0000
     1.3 @@ -0,0 +1,89 @@
     1.4 +# Options related to paths and install
     1.5 +
     1.6 +comment "Paths"
     1.7 +
     1.8 +config LOCAL_TARBALLS_DIR
     1.9 +    string
    1.10 +    prompt "Local tarballs directory"
    1.11 +    default ""
    1.12 +    help
    1.13 +      If you have previously downloaded the tarballs, enter the PATH where
    1.14 +      you stored them here.
    1.15 +
    1.16 +config SAVE_TARBALLS
    1.17 +    bool
    1.18 +    prompt "Save new tarballs"
    1.19 +    default n
    1.20 +    depends on LOCAL_TARBALLS_DIR != ""
    1.21 +    help
    1.22 +      If you say 'y' here, new downloaded tarballs will be saved in the
    1.23 +      directory you entered above.
    1.24 +
    1.25 +config PREFIX_DIR
    1.26 +    string
    1.27 +    prompt "Prefix directory"
    1.28 +    default "${HOME}/${CT_TARGET}"
    1.29 +    help
    1.30 +      This is the path the toolchain will run from.
    1.31 +
    1.32 +config INSTALL_DIR
    1.33 +    string
    1.34 +#    prompt "Install directory"
    1.35 +    default "${CT_PREFIX_DIR}"
    1.36 +#    help
    1.37 +#      This is the path the target will be installed into.
    1.38 +#      
    1.39 +#      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
    1.40 +#      you can't write there, you can install somewhere else and have a third
    1.41 +#      person do the install for you.
    1.42 +#      The reason you might also want to install elsewhere is if you are going
    1.43 +#      to package your shinny new toolchain for distribution.
    1.44 +
    1.45 +config CUSTOM_PATCH
    1.46 +    bool
    1.47 +    prompt "Use custom patch directory"
    1.48 +    default n
    1.49 +    help
    1.50 +      If you have custom patches that you want to be applied, say 'Y' here and
    1.51 +      enter the path directory below.
    1.52 +      
    1.53 +      Note that you must ensure that the patch directory is arranged the same
    1.54 +      way the official directory is.
    1.55 +
    1.56 +config CUSTOM_PATCH_ONLY
    1.57 +    bool
    1.58 +    prompt "Only use custom patches"
    1.59 +    default n
    1.60 +    depends on CUSTOM_PATCH
    1.61 +    help
    1.62 +      Don't apply patches coming with crosstool-NG, only those patches available
    1.63 +      in the directory below.
    1.64 +      
    1.65 +      If you say 'N' here, then the patches provided with crosstool-NG will be
    1.66 +      applied first, and then your patches.
    1.67 +
    1.68 +config CUSTOM_PATCH_DIR
    1.69 +    string
    1.70 +    prompt "Custom patch directory"
    1.71 +    default ""
    1.72 +    depends on CUSTOM_PATCH
    1.73 +    help
    1.74 +      Enter the custom patch directory here.
    1.75 +
    1.76 +config REMOVE_DOCS
    1.77 +    bool
    1.78 +    prompt "Remove documentation"
    1.79 +    default n
    1.80 +    help
    1.81 +      Remove the installed documentation (man and info pages).
    1.82 +      Gains around 8MiB for a uClibc-based, C and C++ compiler.
    1.83 +
    1.84 +config INSTALL_DIR_RO
    1.85 +    bool
    1.86 +    prompt "Render the toolchain read-only"
    1.87 +    default n
    1.88 +    help
    1.89 +      Render the directory of the toolchain (and its sub-directories)
    1.90 +      read-only.
    1.91 +      
    1.92 +      Usefull for toolchains destined for production.