Allow to store working files outside the build tree (eg. incase the working tree is on the network).

 /trunk/scripts/crosstool.sh   |    9     5     4     0 +++++----
 /trunk/config/global/paths.in |   23    22     1     0 ++++++++++++++++++++++-
 2 files changed, 27 insertions(+), 5 deletions(-)

1 files changed, 22 insertions, 1 deletions

diff --git a/config/global/paths.in b/config/global/paths.in
index 3736d666..0f04f148 100644
--- a/config/global/paths.in
+++ b/config/global/paths.in
@@ -19,6 +19,27 @@ config SAVE_TARBALLS
       If you say 'y' here, new downloaded tarballs will be saved in the
       directory you entered above.
 
+config WORK_DIR
+    string
+    prompt "Working directory"
+    default "${CT_TOP_DIR}/targets"
+    help
+      Set this to the directory where all build actions will be done.
+      
+      The default is "${CT_TOP_DIR}/targets", and leaving this option
+      empty will also use the default.
+      
+      You should not need to change that, except in one very peculiar
+      setup:
+       - your crosstool-NG source directory is on the network
+       - you configured crosstool-NG with --local
+      This kind of setup is a pain, as any action involving source file
+      access would have to go through the wire. In this case, you should
+      set CT_WORK_DIR to point to a path local to your machine, to avoid
+      any network overhead.
+      
+      Do *NOT* change it if you don't know better.
+
 config PREFIX_DIR
     string
     prompt "Prefix directory"
@@ -31,7 +52,7 @@ config INSTALL_DIR
 #    prompt "Install directory"
     default "${CT_PREFIX_DIR}"
 #    help
-#      This is the path the target will be installed into.
+#      This is the path the toolchain will be installed into.
 #      
 #      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
 #      you can't write there, you can install somewhere else and have a third