summaryrefslogtreecommitdiff
path: root/config/ct-behave.in
diff options
context:
space:
mode:
Diffstat (limited to 'config/ct-behave.in')
-rw-r--r--config/ct-behave.in82
1 files changed, 82 insertions, 0 deletions
diff --git a/config/ct-behave.in b/config/ct-behave.in
new file mode 100644
index 0000000..737028b
--- /dev/null
+++ b/config/ct-behave.in
@@ -0,0 +1,82 @@
+# Options specific to crosstool-NG overall behavior
+
+comment "crosstool-NG behavior"
+
+config OBSOLETE
+ bool
+ prompt "Use obsolete features"
+ 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...
+
+config EXPERIMENTAL
+ bool
+ prompt "Try features marked as EXPERIMENTAL"
+ default n
+ 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
+ - unfinished, in which case you could try hacking it and send me the result
+ - non-existant, in which case you could also try hacking it in and send me
+ the result
+
+config BROKEN
+ bool
+ prompt "Try broken stuff"
+ default n
+ depends on EXPERIMENTAL
+ help
+ Select this if you want to _debug_ broken stuff.
+
+config DEBUG_CT
+ bool
+ prompt "Debug crosstool-NG"
+ default n
+ help
+ Say 'y' here to get some debugging options
+
+if DEBUG_CT
+
+config DEBUG_CT_PAUSE_STEPS
+ bool
+ prompt "Pause between every steps"
+ default n
+ help
+ Say 'y' if you intend to attend the build, and want to investigate
+ the result of each steps before running the next one.
+
+config DEBUG_CT_SAVE_STEPS
+ bool
+ prompt "Save intermediate steps"
+ default n
+ 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.
+ They are treated as a whole.
+
+ See docs/overview.txt for the list of steps.
+
+config DEBUG_CT_SAVE_STEPS_GZIP
+ bool
+ prompt "gzip saved states"
+ default y
+ depends on DEBUG_CT_SAVE_STEPS
+ 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
+ got figures here! :-) ).
+
+endif