config/global/ct-behave.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sat Oct 18 18:37:28 2008 +0000 (2008-10-18)
changeset 945 d0e5f04d2e06
parent 725 d2c46e039cd8
child 1064 492d939dbb19
permissions -rw-r--r--
Extract the config files related stuff from the kconfig stuff
- create config/config.mk, with all the config.gen/ rules
- the only common points between config files and configurators:
- the top-level config file to include, stored in KCONFIG_TOP
- the config_file rules, which makes config files available to configurators
- dependency-files are renamed from %.d to %.dep (.d is reserved for directories)
- a few eye-candy here and there

/trunk/kconfig/kconfig.mk | 184 12 172 0 +++--------------------------------------------------
/trunk/config/config.mk | 118 9 109 0 +++-------------------------------
/trunk/ct-ng.in | 1 1 0 0 +
3 files changed, 22 insertions(+), 281 deletions(-)
     1 # Options specific to crosstool-NG overall behavior
     2 
     3 comment "crosstool-NG behavior"
     4 
     5 config OBSOLETE
     6     bool
     7     prompt "Use obsolete features"
     8     default n
     9     help
    10       If you set this to Y, you will be able to select obsolete features.
    11 
    12       Such obsolete features are the use of old kernel headers, old
    13       gcc versions, etc...
    14 
    15 config EXPERIMENTAL
    16     bool
    17     prompt "Try features marked as EXPERIMENTAL"
    18     default n
    19     help
    20       If you set this to Y, then you will be able to try very experimental
    21       features.
    22 
    23       Experimental features can be one of:
    24         - working, in which case you should tell me it is!
    25         - buggy, in which case you could try patching and send me the result
    26         - unfinished, in which case you could try hacking it and send me the result
    27         - non-existant, in which case you could also try hacking it in and send me
    28           the result
    29 
    30 config DEBUG_CT
    31     bool
    32     prompt "Debug crosstool-NG"
    33     default n
    34     help
    35       Say 'y' here to get some debugging options
    36 
    37 if DEBUG_CT
    38 
    39 config DEBUG_PAUSE_STEPS
    40     bool
    41     prompt "Pause between every steps"
    42     default n
    43     help
    44       Say 'y' if you intend to attend the build, and want to investigate
    45       the result of each steps before running the next one.
    46 
    47 config DEBUG_CT_SAVE_STEPS
    48     bool
    49     prompt "Save intermediate steps"
    50     default n
    51     help
    52       If you say 'y' here, then you will be able to restart crosstool-NG at
    53       any step.
    54 
    55       It is not currently possible to restart at any of the debug facility.
    56       They are treated as a whole.
    57 
    58       See docs/overview.txt for the list of steps.
    59 
    60 config DEBUG_CT_SAVE_STEPS_GZIP
    61     bool
    62     prompt "gzip saved states"
    63     default y
    64     depends on DEBUG_CT_SAVE_STEPS
    65     help
    66       If you are tight on space, then you can ask to gzip the saved states
    67       tarballs. On the other hand, this takes some longer time...
    68 
    69       To lose as less time as possible, the gzip process is done with a low
    70       compression ratio (-3), which gives roughly 70% gain in size. Going
    71       further doesn't gain much, and takes far more time (believe me, I've
    72       got figures here! :-) ).
    73 
    74 endif