1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/config/global/ct-behave.in Fri Apr 18 08:41:30 2008 +0000
1.3 @@ -0,0 +1,82 @@
1.4 +# Options specific to crosstool-NG overall behavior
1.5 +
1.6 +comment "crosstool-NG behavior"
1.7 +
1.8 +config OBSOLETE
1.9 + bool
1.10 + prompt "Use obsolete features"
1.11 + default n
1.12 + help
1.13 + If you set this to Y, you will be able to select obsolete features.
1.14 +
1.15 + Such obsolete features are the use of old kernel headers, old
1.16 + gcc versions, etc...
1.17 +
1.18 +config EXPERIMENTAL
1.19 + bool
1.20 + prompt "Try features marked as EXPERIMENTAL"
1.21 + default n
1.22 + help
1.23 + If you set this to Y, then you will be able to try very experimental
1.24 + features.
1.25 +
1.26 + Experimental features can be one of:
1.27 + - working, in which case you should tell me it is!
1.28 + - buggy, in which case you could try patching and send me the result
1.29 + - unfinished, in which case you could try hacking it and send me the result
1.30 + - non-existant, in which case you could also try hacking it in and send me
1.31 + the result
1.32 +
1.33 +config BROKEN
1.34 + bool
1.35 + prompt "Try broken stuff"
1.36 + default n
1.37 + depends on EXPERIMENTAL
1.38 + help
1.39 + Select this if you want to _debug_ broken stuff.
1.40 +
1.41 +config DEBUG_CT
1.42 + bool
1.43 + prompt "Debug crosstool-NG"
1.44 + default n
1.45 + help
1.46 + Say 'y' here to get some debugging options
1.47 +
1.48 +if DEBUG_CT
1.49 +
1.50 +config DEBUG_CT_PAUSE_STEPS
1.51 + bool
1.52 + prompt "Pause between every steps"
1.53 + default n
1.54 + help
1.55 + Say 'y' if you intend to attend the build, and want to investigate
1.56 + the result of each steps before running the next one.
1.57 +
1.58 +config DEBUG_CT_SAVE_STEPS
1.59 + bool
1.60 + prompt "Save intermediate steps"
1.61 + default n
1.62 + help
1.63 + If you say 'y' here, then you will be able to restart crosstool-NG at
1.64 + any step.
1.65 +
1.66 + It is not currently possible to restart at any of the debug facility.
1.67 + They are treated as a whole.
1.68 +
1.69 + See docs/overview.txt for the list of steps.
1.70 +
1.71 +config DEBUG_CT_SAVE_STEPS_GZIP
1.72 + bool
1.73 + prompt "gzip saved states"
1.74 + default y
1.75 + depends on DEBUG_CT_SAVE_STEPS
1.76 + help
1.77 + If you are tight on space, then you can ask to gzip the saved states
1.78 + tarballs. On the other hand, this takes some longer time...
1.79 +
1.80 + To lose as less time as possible, the gzip process is done with a low
1.81 + compression ratio (-3), which gives roughly 70% gain in size. Going
1.82 + further doesn't gain much, and takes far more time (believe me, I've
1.83 + got figures here! :-) ).
1.84 +
1.85 +endif