config/global/ct-behave.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Oct 09 19:17:49 2008 +0000 (2008-10-09)
changeset 914 0b164a321177
parent 725 d2c46e039cd8
child 1064 492d939dbb19
permissions -rw-r--r--
Remove CT_BROKEN.
Only one component is actually BROKEN (libelf), make it depend on EXPERIMENTAL, but state BROKEN in the prompt.
ltrace (which depends on libelf) is now marked as EXPERIMENTAL, with the reference to the BROKEN libelf in the help entry.

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