config/toolchain.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun May 13 21:11:27 2007 +0000 (2007-05-13)
changeset 91 aa1d248fa51b
parent 47 7e2539937b6e
child 96 aa1a9fbd6eb8
permissions -rw-r--r--
Remove dead entries for components not yet integrated: cygwin kernel, tcc...
Some fixups in config entries, to avoid warnings when parsed by the kconfig parser.
     1 menu "Toolchain options"
     2 
     3 comment "General toolchain options"
     4 
     5 config USE_SYSROOT
     6     bool
     7     prompt "Use sysroot'ed toolchain"
     8     default y
     9     help
    10       Use the 'shinny new' sysroot feature of gcc: libraries split between
    11       prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
    12       
    13       You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
    14 
    15 config SHARED_LIBS
    16     bool
    17     prompt "Build shared libraries"
    18     default y
    19     help
    20       Say 'y' here, unless you don't want shared libraries.
    21       
    22       You might not want shared librries if you're building for a target that
    23       don't support it (maybe some nommu targets, for example, or bare metal).
    24 
    25 config TARGET_MULTILIB
    26     bool
    27 #    prompt "Enable 'multilib' support (EXPERIMENTAL)"
    28     default n
    29     help
    30       Enable the so-called 'multilib' support.
    31       
    32       With the same toolchain, and on some architectures, you will be able to
    33       build big and little endian binaries, soft- and hard-float, etc...
    34       
    35       See the gcc configure manual at http://gcc.gnu.org/install/configure.html
    36       to see what multilib your target supports.
    37       
    38       It's preferable for now to build two (or more) toolchains, one for each
    39       configuration you need to support (eg. one for thumb and one for ARM,
    40       etc...). You can use the vendor string to diferentiate those toolchains.
    41 
    42 config TARGET_VENDOR
    43     string
    44     prompt "Vendor string"
    45     default "unknown"
    46     help
    47       Vendor part of the machine triplet.
    48       
    49       A triplet is of the form arch-vendor-kernel-system.
    50       You can set the second part, vendor, to whatever you see fit.
    51       Use a single word, or use underscores "_" to separate words.
    52       
    53       Keep the default (unkown) if you don't know better.
    54 
    55 config TARGET_ALIAS
    56     string
    57     prompt "Target alias"
    58     default ""
    59     help
    60       Normaly, you'd call your toolchain component (especially gcc) by
    61       prefixing the target triplet followed by a dash and the component name
    62       (eg. armeb-unknown-linux-uclibc-gcc).
    63       
    64       You can enter a shortcut here. This string will be used to create
    65       symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
    66       then gcc for your toolchain will also be available as "foo-bar-gcc" along
    67       with the original name).
    68       
    69       You shouldn't need to enter anything here, unless you plan to manually
    70       call the tools (autotools-based ./configure will use the standard name).
    71 
    72 comment "Toolchain type"
    73 
    74 choice
    75     bool
    76     prompt "Type"
    77     default CROSS
    78 
    79 config NATIVE
    80     bool
    81     prompt "Native (EXPERIMENTAL)"
    82     depends on EXPERIMENTAL
    83     help
    84       Build a native toolchain.
    85       See docs/overview.txt
    86 
    87 config CROSS
    88     bool
    89     prompt "Cross"
    90     help
    91       Build a cross-toolchain.
    92       See docs/overview.txt
    93 
    94 config CROSS_NATIVE
    95     bool
    96     prompt "Croos-native (EXPERIMENTAL)"
    97     depends on EXPERIMENTAL
    98     help
    99       Build a cross-native toolchain.
   100       See docs/overview.txt
   101 
   102 config CANADIAN
   103     bool
   104     prompt "Canadian (EXPERIMENTAL)"
   105     depends on EXPERIMENTAL
   106     help
   107       Build a canadian-toolchain.
   108       See docs/overview.txt
   109 
   110 endchoice
   111 
   112 config BUILD 
   113     string
   114     prompt "Build system triplet"
   115     default ""
   116     help
   117       Canonical name of the machine building the toolchain.
   118       You should leave empty, unless you really now what you're doing.
   119 
   120 config CC_NATIVE
   121     string
   122     prompt "Native gcc"
   123     default "gcc"
   124     help
   125       The native C compiler.
   126       
   127       You can set this to an alternative compiler if you have more than one
   128       installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
   129       
   130       You can leave this empty as well, in which case gcc will be used.
   131 
   132 config HOST
   133     string
   134     prompt "Host system triplet"
   135     default ""
   136     depends on NATIVE || CANADIAN
   137     help
   138       Canonical name of the machine running the toolchain.
   139 
   140 config HOST_CC
   141     string
   142     prompt "Cross-compiler prefix for host system"
   143     default "${CT_HOST}-"
   144     depends on NATIVE || CANADIAN
   145     help
   146       C compiler targeting the host system.
   147 
   148 config TARGET_CC
   149     string
   150     prompt "Cross-compiler prefix for target system"
   151     default "${CT_TARGET}-"
   152     depends on CANADIAN
   153     help
   154       C compiler targeting the target system.
   155 
   156 endmenu