config/toolchain.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Aug 21 13:12:35 2008 +0000 (2008-08-21)
changeset 803 1787813fc62a
parent 802 4c6b50e0021a
child 850 ef8549b58b6f
permissions -rw-r--r--
Typo.

/trunk/config/toolchain.in | 2 1 1 0 +-
1 file changed, 1 insertion(+), 1 deletion(-)
yann@41
     1
menu "Toolchain options"
yann@41
     2
yann@41
     3
comment "General toolchain options"
yann@41
     4
yann@41
     5
config USE_SYSROOT
yann@41
     6
    bool
yann@41
     7
    prompt "Use sysroot'ed toolchain"
yann@41
     8
    default y
yann@41
     9
    help
yann@41
    10
      Use the 'shinny new' sysroot feature of gcc: libraries split between
yann@41
    11
      prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
yann@41
    12
      
yann@41
    13
      You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
yann@41
    14
yann@41
    15
config SHARED_LIBS
yann@41
    16
    bool
yann@41
    17
    prompt "Build shared libraries"
yann@41
    18
    default y
yann@41
    19
    help
yann@41
    20
      Say 'y' here, unless you don't want shared libraries.
yann@41
    21
      
yann@803
    22
      You might not want shared libraries if you're building for a target that
yann@41
    23
      don't support it (maybe some nommu targets, for example, or bare metal).
yann@41
    24
yann@41
    25
config TARGET_VENDOR
yann@41
    26
    string
yann@41
    27
    prompt "Vendor string"
yann@41
    28
    default "unknown"
yann@41
    29
    help
yann@335
    30
      Vendor part of the target tuple.
yann@41
    31
      
yann@335
    32
      A tuple is of the form arch-vendor-kernel-system.
yann@41
    33
      You can set the second part, vendor, to whatever you see fit.
yann@41
    34
      Use a single word, or use underscores "_" to separate words.
yann@41
    35
      
yann@41
    36
      Keep the default (unkown) if you don't know better.
yann@41
    37
yann@321
    38
config TARGET_ALIAS_SED_EXPR
yann@321
    39
    string
yann@321
    40
    prompt "Target sed transform"
yann@321
    41
    default ""
yann@321
    42
    help
yann@321
    43
      Normaly, you'd call your toolchain components (especially gcc) by
yann@335
    44
      prefixing the target tuple followed by a dash and the component name
yann@321
    45
      (eg. armeb-unknown-linux-uclibc-gcc).
yann@321
    46
      
yann@321
    47
      You can enter here a sed expression to be applied to ${CT_TARGET} to
yann@321
    48
      create an alias for your toolchain.
yann@321
    49
      
yann@321
    50
      For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
yann@321
    51
      will create the armeb-foobar-linux-uclibc alias to the above-mentioned
yann@321
    52
      toolchain.
yann@321
    53
      
yann@321
    54
      You shouldn't need to enter anything here, unless you plan to manually
yann@321
    55
      call the tools (autotools-based ./configure will use the standard name).
yann@321
    56
yann@41
    57
config TARGET_ALIAS
yann@41
    58
    string
yann@41
    59
    prompt "Target alias"
yann@41
    60
    default ""
yann@41
    61
    help
yann@321
    62
      Normaly, you'd call your toolchain components (especially gcc) by
yann@335
    63
      prefixing the target tuple followed by a dash and the component name
yann@41
    64
      (eg. armeb-unknown-linux-uclibc-gcc).
yann@41
    65
      
yann@41
    66
      You can enter a shortcut here. This string will be used to create
yann@41
    67
      symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
yann@41
    68
      then gcc for your toolchain will also be available as "foo-bar-gcc" along
yann@41
    69
      with the original name).
yann@41
    70
      
yann@41
    71
      You shouldn't need to enter anything here, unless you plan to manually
yann@41
    72
      call the tools (autotools-based ./configure will use the standard name).
yann@41
    73
yann@41
    74
comment "Toolchain type"
yann@41
    75
yann@41
    76
choice
yann@41
    77
    bool
yann@41
    78
    prompt "Type"
yann@41
    79
    default CROSS
yann@41
    80
yann@41
    81
config NATIVE
yann@41
    82
    bool
yann@41
    83
    prompt "Native (EXPERIMENTAL)"
yann@41
    84
    depends on EXPERIMENTAL
yann@41
    85
    help
yann@41
    86
      Build a native toolchain.
yann@41
    87
      See docs/overview.txt
yann@41
    88
yann@41
    89
config CROSS
yann@41
    90
    bool
yann@41
    91
    prompt "Cross"
yann@41
    92
    help
yann@41
    93
      Build a cross-toolchain.
yann@41
    94
      See docs/overview.txt
yann@41
    95
yann@41
    96
config CROSS_NATIVE
yann@41
    97
    bool
yann@425
    98
    prompt "Cross-native (EXPERIMENTAL)"
yann@41
    99
    depends on EXPERIMENTAL
yann@41
   100
    help
yann@41
   101
      Build a cross-native toolchain.
yann@41
   102
      See docs/overview.txt
yann@41
   103
yann@41
   104
config CANADIAN
yann@41
   105
    bool
yann@41
   106
    prompt "Canadian (EXPERIMENTAL)"
yann@41
   107
    depends on EXPERIMENTAL
yann@41
   108
    help
yann@41
   109
      Build a canadian-toolchain.
yann@41
   110
      See docs/overview.txt
yann@41
   111
yann@41
   112
endchoice
yann@41
   113
yann@96
   114
config TOOLCHAIN_TYPE
yann@96
   115
    string
yann@96
   116
    default "native"        if NATIVE
yann@96
   117
    default "cross"         if CROSS
yann@96
   118
    default "cross-native"  if CROSS_NATIVE
yann@96
   119
    default "canadian"      if CANADIAN
yann@96
   120
yann@41
   121
config BUILD 
yann@41
   122
    string
yann@335
   123
    prompt "Build system tuple"
yann@41
   124
    default ""
yann@41
   125
    help
yann@41
   126
      Canonical name of the machine building the toolchain.
yann@41
   127
      You should leave empty, unless you really now what you're doing.
yann@41
   128
yann@41
   129
config CC_NATIVE
yann@41
   130
    string
yann@41
   131
    prompt "Native gcc"
yann@41
   132
    default "gcc"
yann@41
   133
    help
yann@41
   134
      The native C compiler.
yann@41
   135
      
yann@41
   136
      You can set this to an alternative compiler if you have more than one
yann@41
   137
      installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
yann@41
   138
      
yann@41
   139
      You can leave this empty as well, in which case gcc will be used.
yann@41
   140
yann@41
   141
config HOST
yann@41
   142
    string
yann@335
   143
    prompt "Host system tuple"
yann@41
   144
    default ""
yann@41
   145
    depends on NATIVE || CANADIAN
yann@41
   146
    help
yann@41
   147
      Canonical name of the machine running the toolchain.
yann@41
   148
yann@41
   149
config HOST_CC
yann@41
   150
    string
yann@41
   151
    prompt "Cross-compiler prefix for host system"
yann@41
   152
    default "${CT_HOST}-"
yann@41
   153
    depends on NATIVE || CANADIAN
yann@41
   154
    help
yann@41
   155
      C compiler targeting the host system.
yann@41
   156
yann@41
   157
config TARGET_CC
yann@41
   158
    string
yann@41
   159
    prompt "Cross-compiler prefix for target system"
yann@41
   160
    default "${CT_TARGET}-"
yann@41
   161
    depends on CANADIAN
yann@41
   162
    help
yann@41
   163
      C compiler targeting the target system.
yann@41
   164
yann@41
   165
endmenu