config/toolchain.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Sep 23 14:48:10 2008 +0000 (2008-09-23)
changeset 872 fd4bf138f08f
parent 803 1787813fc62a
child 1041 2573519c00d6
permissions -rw-r--r--
Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.

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