yann@445: # Options specific to crosstool-NG overall behavior yann@1: yann@197: comment "crosstool-NG behavior" yann@121: yann@244: config OBSOLETE yann@244: bool yann@244: prompt "Use obsolete features" yann@244: default n yann@244: help yann@244: If you set this to Y, you will be able to select obsolete features. yann@445: yann@244: Such obsolete features are the use of old kernel headers, old yann@244: gcc versions, etc... yann@244: yann@41: config EXPERIMENTAL yann@41: bool yann@41: prompt "Try features marked as EXPERIMENTAL" yann@41: default n yann@41: help yann@41: If you set this to Y, then you will be able to try very experimental yann@41: features. yann@445: yann@41: Experimental features can be one of: yann@41: - working, in which case you should tell me it is! yann@41: - buggy, in which case you could try patching and send me the result yann@41: - unfinished, in which case you could try hacking it and send me the result yann@384: - non-existant, in which case you could also try hacking it in and send me yann@384: the result yann@41: yann@244: config BROKEN yann@61: bool yann@244: prompt "Try broken stuff" yann@61: default n yann@244: depends on EXPERIMENTAL yann@61: help yann@244: Select this if you want to _debug_ broken stuff. yann@61: yann@121: config DEBUG_CT yann@121: bool yann@121: prompt "Debug crosstool-NG" yann@121: default n yann@121: help yann@121: Say 'y' here to get some debugging options yann@121: yann@121: if DEBUG_CT yann@121: yann@725: config DEBUG_PAUSE_STEPS yann@121: bool yann@121: prompt "Pause between every steps" yann@121: default n yann@121: help yann@121: Say 'y' if you intend to attend the build, and want to investigate yann@121: the result of each steps before running the next one. yann@121: yann@121: config DEBUG_CT_SAVE_STEPS yann@121: bool yann@121: prompt "Save intermediate steps" yann@121: default n yann@121: help yann@121: If you say 'y' here, then you will be able to restart crosstool-NG at yann@168: any step. yann@445: yann@445: It is not currently possible to restart at any of the debug facility. yann@168: They are treated as a whole. yann@168: yann@168: See docs/overview.txt for the list of steps. yann@121: yann@121: config DEBUG_CT_SAVE_STEPS_GZIP yann@121: bool yann@121: prompt "gzip saved states" yann@121: default y yann@121: depends on DEBUG_CT_SAVE_STEPS yann@121: help yann@121: If you are tight on space, then you can ask to gzip the saved states yann@121: tarballs. On the other hand, this takes some longer time... yann@445: yann@121: To lose as less time as possible, the gzip process is done with a low yann@121: compression ratio (-3), which gives roughly 70% gain in size. Going yann@121: further doesn't gain much, and takes far more time (believe me, I've yann@121: got figures here! :-) ). yann@121: yann@121: endif