1.1 --- a/config/global/paths.in Sun Sep 12 21:38:12 2010 +0200
1.2 +++ b/config/global/paths.in Mon Apr 04 01:00:17 2011 +0200
1.3 @@ -61,6 +61,28 @@
1.4 # The reason you might also want to install elsewhere is if you are going
1.5 # to package your shinny new toolchain for distribution.
1.6
1.7 +config RM_RF_PREFIX_DIR
1.8 + bool
1.9 + prompt "| Remove the prefix dir prior to building"
1.10 + default y
1.11 + depends on !BACKEND
1.12 + help
1.13 + If you say 'y' here, then PREFIX_DIR (above) will be eradicated
1.14 + prior to the toolchain is built.
1.15 +
1.16 + This can be usefull when you are trying different settings (due
1.17 + to build failures or feature tests). In this case, to avoid using
1.18 + a potentially broken previous toolchain, the install location is
1.19 + removed, to start afresh.
1.20 +
1.21 + On the oher hand, if you are building a final toolchain, and install
1.22 + it into a directory with pre-install, unrelated programs, it would be
1.23 + damageable to remove that directory. In this case, you may want to
1.24 + say 'n' here.
1.25 +
1.26 + Note that when acting as a backend, this option is not available, and
1.27 + is forced to 'n'.
1.28 +
1.29 config REMOVE_DOCS
1.30 bool
1.31 prompt "Remove documentation"