config/global/ct-behave.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Mar 05 09:19:56 2010 +0100 (2010-03-05)
changeset 1842 2535545dd450
parent 1300 7acdd1de5b50
child 1867 dc39960ecfd2
permissions -rw-r--r--
config: prepare for build-system backend

When acting as a backend for a build-system, we should not build
any application that runs on the target, that is:
- no native gdb
- no companion libraries
- no binutils libraries
- no debug tools (save for gdbserver)
- ...

Here, we simply prepare the (hidden) config option that will detect
that we are acting as a back-end.

Update doc accordingly.
     1 # Options specific to crosstool-NG overall behavior
     2 
     3 comment "crosstool-NG behavior"
     4 
     5 config IS_A_BACKEND
     6     string
     7     option env="CT_IS_A_BACKEND"
     8 
     9 config BACKEND
    10     bool
    11     default y if IS_A_BACKEND =  "y" || IS_A_BACKEND =  "Y"
    12     default n if IS_A_BACKEND != "y" && IS_A_BACKEND != "Y"
    13 
    14 config OBSOLETE
    15     bool
    16     prompt "Use obsolete features"
    17     default n
    18     help
    19       If you set this to Y, you will be able to select obsolete features.
    20       
    21       Such obsolete features are the use of old kernel headers, old gcc
    22       versions, etc... for which maintaining support in crosstool-NG
    23       would be very costly.
    24       
    25       It does not however mean that the specific feature or version has been
    26       marked obsolete by the upstream team.
    27 
    28 config EXPERIMENTAL
    29     bool
    30     prompt "Try features marked as EXPERIMENTAL"
    31     default n
    32     help
    33       If you set this to Y, then you will be able to try very experimental
    34       features.
    35       
    36       Experimental features can be one of:
    37         - working, in which case you should tell me it is!
    38         - buggy, in which case you could try patching and send me the result
    39         - unfinished, in which case you could try hacking it and send me the result
    40         - non-existant, in which case you could also try hacking it in and send me
    41           the result
    42 
    43 config DEBUG_CT
    44     bool
    45     prompt "Debug crosstool-NG"
    46     default n
    47     help
    48       Say 'y' here to get some options regarding debugging crosstool-NG.
    49 
    50 if DEBUG_CT
    51 
    52 config DEBUG_PAUSE_STEPS
    53     bool
    54     prompt "Pause between every steps"
    55     default n
    56     help
    57       Say 'y' if you intend to attend the build, and want to investigate
    58       the result of each steps before running the next one.
    59 
    60 config DEBUG_CT_SAVE_STEPS
    61     bool
    62     prompt "Save intermediate steps"
    63     default n
    64     help
    65       If you say 'y' here, then you will be able to restart crosstool-NG at
    66       any step.
    67       
    68       It is not currently possible to restart at any of the debug facilities.
    69       They are treated as a whole.
    70       
    71       See docs/overview.txt for the list of steps.
    72 
    73 config DEBUG_CT_SAVE_STEPS_GZIP
    74     bool
    75     prompt "gzip saved states"
    76     default y
    77     depends on DEBUG_CT_SAVE_STEPS
    78     help
    79       If you are tight on space, then you can ask to gzip the saved states
    80       tarballs. On the other hand, this takes some longer time...
    81       
    82       To lose as less time as possible, the gzip process is done with a low
    83       compression ratio (-3), which gives roughly 70% gain in size. Going
    84       further doesn't gain much, and takes far more time (believe me, I've
    85       got figures here! :-) ).
    86 
    87 config NO_OVERIDE_LC_MESSAGES
    88     bool
    89     prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
    90     depends on EXPERIMENTAL
    91     default n
    92     help
    93       By default, crosstool-NG sets and exports LC_ALL=C so that the
    94       build.log file contains english messages, that can be read by
    95       people most likely to help interpret the logs. If you say N here,
    96       and your locale is not an english language, then dissecting your
    97       log file will be difficult for most people but you.
    98       
    99       If you say Y here, then your current locale settings will be used
   100       to print messages, instead of plain english.
   101       
   102       Say N, please.
   103 
   104 endif