config/kernel.in
author Bart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
branch1.7
changeset 2046 471acb219d77
parent 1502 472cfde636a1
child 1976 2d90ec981ba3
permissions -rw-r--r--
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
(transplanted from 3917f2dafed1bb189e39f50e8506b3141926d7e1)
     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     default n
    10 
    11 # Each target OS (aka kernel) that support shared libraries can select
    12 # this, so the user can decide whether or not to build a shared library
    13 # enabled toolchain
    14 config KERNEL_SUPPORTS_SHARED_LIBS
    15     bool
    16     default n
    17 
    18 config KERNEL
    19     string
    20 
    21 config KERNEL_VERSION
    22     string
    23 
    24 source "config.gen/kernel.in"
    25 
    26 comment "Common kernel options"
    27 
    28 config SHARED_LIBS
    29     bool
    30     prompt "Build shared libraries"
    31     depends on KERNEL_SUPPORTS_SHARED_LIBS
    32     default y
    33     help
    34       Say 'y' here, unless you don't want shared libraries.
    35       
    36       You might not want shared libraries if you're building for a target that
    37       don't support it (maybe some nommu targets, for example, or bare metal).
    38 
    39 endmenu