ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2025-04-09 04:14:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL.

Browse Source 
-------- diffstat follows --------
 /trunk/config/global/ct-behave.in |   22    13     9     0 +++++++++++++---------
 /trunk/docs/overview.txt          |    8     6     2     0 ++++++--
 2 files changed, 19 insertions(+), 11 deletions(-)
This commit is contained in:
Yann E. MORIN" 2009-04-20 21:30:25 +00:00
parent 1805f4e62d
commit 683d230777
2 changed files with 19 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
config/global/ct-behave.in
View File

@ -8,9 +8,13 @@ config OBSOLETE
default n
help
If you set this to Y, you will be able to select obsolete features.
Such obsolete features are the use of old kernel headers, old
gcc versions, etc...
Such obsolete features are the use of old kernel headers, old gcc
versions, etc... for which maintaining support in crosstool-NG
would be very costly.
It does not however mean that the specific feature or version has been
marked obsolete by the upstream team.
config EXPERIMENTAL
bool
@ -19,7 +23,7 @@ config EXPERIMENTAL
help
If you set this to Y, then you will be able to try very experimental
features.
Experimental features can be one of:
- working, in which case you should tell me it is!
- buggy, in which case you could try patching and send me the result
@ -32,7 +36,7 @@ config DEBUG_CT
prompt "Debug crosstool-NG"
default n
help
Say 'y' here to get some debugging options
Say 'y' here to get some options regarding debugging crosstool-NG.
if DEBUG_CT
@ -51,10 +55,10 @@ config DEBUG_CT_SAVE_STEPS
help
If you say 'y' here, then you will be able to restart crosstool-NG at
any step.
It is not currently possible to restart at any of the debug facility.
It is not currently possible to restart at any of the debug facilities.
They are treated as a whole.
See docs/overview.txt for the list of steps.
config DEBUG_CT_SAVE_STEPS_GZIP
@ -65,7 +69,7 @@ config DEBUG_CT_SAVE_STEPS_GZIP
help
If you are tight on space, then you can ask to gzip the saved states
tarballs. On the other hand, this takes some longer time...
To lose as less time as possible, the gzip process is done with a low
compression ratio (-3), which gives roughly 70% gain in size. Going
further doesn't gain much, and takes far more time (believe me, I've

8
docs/overview.txt
View File

@ -277,13 +277,17 @@ CT_OBSOLETE:
Show obsolete versions or tools. Most of the time, you don't want to base
your toolchain on too old a version (of gcc, for example). But at times, it
can come handy to use such an old version for regression tests. Those old
versions are hidden behind CT_OBSOLETE.
versions are hidden behind CT_OBSOLETE. Those versions (or features) are so
marked because maintaining support for those in crosstool-NG would be too
costly, time-wise, and time is dear.
CT_EXPERIMENTAL:
Show experimental versions or tools. Again, you might not want to base your
toolchain on too recent tools (eg. gcc) for production. But if you need a
feature present only in a recent version, or a new tool, you can find them
hidden behind CT_EXPERIMENTAL.
hidden behind CT_EXPERIMENTAL. Those versions (or features) did not (yet)
receive thorough testing in crosstool-NG, and/or are not mature enough to
be blindly trusted.
Re-building an existing toolchain |
----------------------------------+