Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/libc/newlib.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 1780 9c03c1a508d8
child 2444 896cb0d36c1a
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # newlib options

     2 # depends on BARE_METAL

     3 

     4 config LIBC_newlib

     5     select LIBC_SUPPORT_THREADS_NONE

     6     help

     7       Newlib is a C library intended for use on embedded systems. It is a

     8       conglomeration of several library parts, all under free software

     9       licenses that make them easily usable on embedded products. Newlib

    10       is only available in source form. It can be compiled for a wide

    11       array of processors, and will usually work on any architecture with

    12       the addition of a few low-level routines.

    13 

    14 choice

    15     bool

    16     prompt "newlib version"

    17 # Don't remove next line

    18 # CT_INSERT_VERSION_BELOW

    19 

    20 config LIBC_NEWLIB_V_1_18_0

    21     bool

    22     prompt "1.18.0 (EXPERIMENTAL)"

    23     depends on EXPERIMENTAL

    24 

    25 config LIBC_NEWLIB_V_1_17_0

    26     bool

    27     prompt "1.17.0"

    28 

    29 config LIBC_NEWLIB_CVS

    30     bool

    31     prompt "Use CVS snapshot"

    32     help

    33       The newlib "team" rolls new releases about once a year (december).

    34       This is quite a long time between releases, in case code was fixed.

    35       

    36       Saying 'Y' here will allow you to use the bleeding-edge code from

    37       the CVS repository. This may or may not fix your issues, may or may

    38       not build, may or may not crash your machine, may or may not withdraw

    39       money from your bank account, may or may not date your girlfriend,

    40       may or may not resurect Elvis... :-)

    41       

    42       In a word: use the CVS snapshot at your own risk! 

    43 

    44 endchoice

    45 

    46 config LIBC_VERSION

    47     string

    48     prompt "use CVS tag" if LIBC_NEWLIB_CVS

    49 # Don't remove next line

    50 # CT_INSERT_VERSION_STRING_BELOW

    51     default "1.18.0" if LIBC_NEWLIB_V_1_18_0

    52     default "1.17.0" if LIBC_NEWLIB_V_1_17_0

    53     help

    54       Enter the tag you want to use.

    55       Leave empty to use the 'head' of the repository.

    56 

    57 comment "Architecture specific options"

    58 

    59 config ATMEL_AVR32_HEADERS

    60     bool

    61     prompt "Install Atmel AVR32 headers"

    62     depends on ARCH_avr32

    63     default y

    64     help

    65       Install Atmel AVR32 headers for native AVR32 development. Most

    66       AVR32 MCU devices are supported.

    67       

    68       If you do native AVR32 development you want to say 'Y' here.
crosstool-ng