config/kernel.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Wed Dec 05 20:31:43 2012 +0100 (2012-12-05)
changeset 3134 863723936e24
parent 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts/xldd: use user's sed and grep

xldd uses sed and grep as detected by ./configure. This works well if is
used on the machine that build the toolchain.

But if the user moves the toolchain to another machine where sed and grep
are not in the same directory (eg. /bin/sed vs. /usr/bin/sed), then xldd
will stop functionning.

Fix that by using ${SED} and ${GREP} if they are set in the environment.

Reported-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
     1 # Kernel options
     2 
     3 menu "Operating System"
     4 
     5 # Config option used throughout the config and code to determine wether
     6 # we have a kernel or not (there might be different bare metal stuff)...
     7 config BARE_METAL
     8     bool
     9 
    10 config WINDOWS
    11     bool
    12 
    13 # Each target OS (aka kernel) that support shared libraries can select
    14 # this, so the user can decide whether or not to build a shared library
    15 # enabled toolchain
    16 config KERNEL_SUPPORTS_SHARED_LIBS
    17     bool
    18 
    19 config KERNEL
    20     string
    21 
    22 config KERNEL_VERSION
    23     string
    24 
    25 source "config.gen/kernel.in"
    26 
    27 comment "Common kernel options"
    28 
    29 config SHARED_LIBS
    30     bool
    31     prompt "Build shared libraries"
    32     depends on KERNEL_SUPPORTS_SHARED_LIBS
    33     default y
    34     help
    35       Say 'y' here, unless you don't want shared libraries.
    36       
    37       You might not want shared libraries if you're building for a target that
    38       don't support it (maybe some nommu targets, for example, or bare metal).
    39 
    40 source "config.gen/kernel.in.2"
    41 
    42 endmenu