config/toolchain.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Sep 06 11:47:40 2009 +0200 (2009-09-06)
changeset 1515 545179329bc5
parent 1514 461d964d7df2
child 1704 6df0d71a7a55
permissions -rw-r--r--
tools wrapper: move choice selection to a more appropriate place

Move the tools wrapper choice selection down to the companion libraries
sub-menu, to avoid the user going back and forth in the menu.
     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 SYSROOT_DIR_PREFIX
    16     string
    17     prompt "sysroot prefix dir (READ HELP)"
    18     depends on USE_SYSROOT
    19     default ""
    20     help
    21       *
    22       * Unless you realy know you need that, leave it empty!
    23       *
    24       
    25       This string will be interpreted as a directory component to be added
    26       to the sysroot path, just before the actual sysroot directory.
    27       
    28       In fact, the sysroot path is constructed as:
    29         ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root
    30 
    31 comment "Tuple completion and aliasing"
    32 
    33 config TARGET_VENDOR
    34     string
    35     prompt "Tuple's vendor string"
    36     default "unknown"
    37     help
    38       Vendor part of the target tuple.
    39       
    40       A tuple is of the form arch-vendor-kernel-system.
    41       You can set the second part, vendor, to whatever you see fit.
    42       Use a single word, or use underscores "_" to separate words.
    43       Use neither dash nor space, as it breaks things.
    44       
    45       Keep the default (unkown) if you don't know better.
    46 
    47 config TARGET_ALIAS_SED_EXPR
    48     string
    49     prompt "Tuple's sed transform"
    50     default ""
    51     help
    52       Normaly, you'd call your toolchain components (especially gcc) by
    53       prefixing the target tuple followed by a dash and the component name
    54       (eg. armeb-unknown-linux-uclibc-gcc).
    55       
    56       You can enter here a sed expression to be applied to ${CT_TARGET} to
    57       create an alias for your toolchain.
    58       
    59       For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
    60       will create the armeb-foobar-linux-uclibc alias to the above-mentioned
    61       toolchain.
    62       
    63       You shouldn't need to enter anything here, unless you plan to manually
    64       call the tools (autotools-based ./configure will use the standard name).
    65 
    66 config TARGET_ALIAS
    67     string
    68     prompt "Tuple's alias"
    69     default ""
    70     help
    71       Normaly, you'd call your toolchain components (especially gcc) by
    72       prefixing the target tuple followed by a dash and the component name
    73       (eg. armeb-unknown-linux-uclibc-gcc).
    74       
    75       You can enter a shortcut here. This string will be used to create
    76       symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
    77       then gcc for your toolchain will also be available as "foo-bar-gcc" along
    78       with the original name).
    79       
    80       You shouldn't need to enter anything here, unless you plan to manually
    81       call the tools (autotools-based ./configure will use the standard name).
    82 
    83 comment "Toolchain type"
    84 
    85 choice
    86     bool
    87     prompt "Type"
    88     default CROSS
    89 
    90 config NATIVE
    91     bool
    92     prompt "Native       (NO CODE!) (EXPERIMENTAL)"
    93     depends on EXPERIMENTAL
    94     help
    95       Build a native toolchain.
    96       See docs/overview.txt
    97 
    98 config CROSS
    99     bool
   100     prompt "Cross"
   101     help
   102       Build a cross-toolchain.
   103       See docs/overview.txt
   104 
   105 config CROSS_NATIVE
   106     bool
   107     prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
   108     depends on EXPERIMENTAL
   109     help
   110       Build a cross-native toolchain.
   111       See docs/overview.txt
   112 
   113 config CANADIAN
   114     bool
   115     prompt "Canadian     (EXPERIMENTAL)"
   116     depends on EXPERIMENTAL
   117     help
   118       Build a canadian-toolchain.
   119       See docs/overview.txt
   120 
   121 endchoice
   122 
   123 config TOOLCHAIN_TYPE
   124     string
   125     default "native"        if NATIVE
   126     default "cross"         if CROSS
   127     default "cross-native"  if CROSS_NATIVE
   128     default "canadian"      if CANADIAN
   129 
   130 comment "Build system"
   131 
   132 config BUILD 
   133     string
   134     prompt "|  Tuple        (READ HELP!)"
   135     default ""
   136     help
   137       Canonical name of the machine building the toolchain.
   138       You should leave empty, unless you really now what you're doing.
   139 
   140 config BUILD_PREFIX
   141     string
   142     prompt "|  Tools prefix (READ HELP!)"
   143     default ""
   144     help
   145       If you have your *build system* tools in a weird location, and/or
   146       they have an unusual prefix, enter it here.
   147       
   148       Usually, you should leave that empty!
   149       
   150       Eg.:
   151         If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
   152         should enter:
   153             /opt/build-tools/bin/weird-
   154         
   155         If your *build* gcc is /opt/build-tools/bin/weird-gcc and
   156         /opt/build-tools/bin is in your PATH, you should enter:
   157             weird-
   158         
   159         If your *build* gcc is /opt/build-tools/bin/gcc then you
   160         should enter (do not forget to add the trailing '/'):
   161             /opt/build-tools/bin/
   162 
   163 config BUILD_SUFFIX
   164     string
   165     prompt "|  Tools suffix (READ HELP!)"
   166     default ""
   167     help
   168       If your *build system* tools have an unusual suffix, enter it
   169       here.
   170       
   171       Usually, you should leave that empty!
   172       
   173       Eg.:
   174         If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
   175         installed as gcc-3.4, then you should enter:
   176             -3.4
   177       
   178       It can happen that some of the tools have a suffix, when others
   179       don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
   180       for that by checking the tools without the suffix in case it can
   181       not find some of the tool.
   182 
   183 if CANADIAN
   184 
   185 comment "Host system"
   186 
   187 config HOST
   188     string
   189     prompt "|  Tuple        (READ HELP!)"
   190     default ""
   191     help
   192       Canonical name of the machine running the toolchain.
   193 
   194 config HOST_PREFIX
   195     string
   196     prompt "|  Tools prefix (READ HELP!)"
   197     default ""
   198     help
   199       If you have your *host system* tools in a weird location, and/or
   200       they have an unusual prefix, enter it here.
   201       
   202       Usually, you should leave that empty!
   203       
   204       Eg.:
   205         If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
   206         should enter:
   207             /opt/host-tools/bin/weird-
   208         
   209         If your *host* gcc is /opt/host-tools/bin/weird-gcc and
   210         /opt/host-tools/bin is in your PATH, you should enter:
   211             weird-
   212         
   213         If your *host* gcc is /opt/host-tools/bin/gcc then you
   214         should enter (do not forget to add the trailing '/'):
   215             /opt/host-tools/bin/
   216 
   217 config HOST_SUFFIX
   218     string
   219     prompt "|  Tools suffix (READ HELP!)"
   220     default ""
   221     help
   222       If your *host system* tools have an unusual suffix, enter it
   223       here.
   224       
   225       Usually, you should leave that empty!
   226       
   227       Eg.:
   228         If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
   229         installed as gcc-3.4, then you should enter:
   230             -3.4
   231       
   232       It can happen that some of the tools have a suffix, when others
   233       don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
   234       for that by checking the tools without the suffix in case it can
   235       not find some of the tool.
   236 
   237 endif # CANADIAN
   238 
   239 if CROSS_NATIVE || CANADIAN
   240 
   241 comment "Target system"
   242 
   243 config TARGET_PREFIX
   244     string
   245     prompt "|  Tools prefix (READ HELP!)"
   246     default ""
   247     help
   248       If you have your *target system* tools in a weird location, and/or
   249       they have an unusual prefix, enter it here.
   250       
   251       Usually, you should leave that empty!
   252       
   253       Eg.:
   254         If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
   255         should enter:
   256             /opt/target-tools/bin/weird-
   257         
   258         If your *target* gcc is /opt/target-tools/bin/weird-gcc and
   259         /opt/target-tools/bin is in your PATH, you should enter:
   260             weird-
   261         
   262         If your *target* gcc is /opt/target-tools/bin/gcc then you
   263         should enter (do not forget to add the trailing '/'):
   264             /opt/target-tools/bin/
   265 
   266 config TARGET_SUFFIX
   267     string
   268     prompt "|  Tools suffix (READ HELP!)"
   269     default ""
   270     help
   271       If your *target system* tools have an unusual suffix, enter it
   272       here.
   273       
   274       Usually, you should leave that empty!
   275       
   276       Eg.:
   277         If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
   278         installed as gcc-3.4, then you should enter:
   279             -3.4
   280       
   281       It can happen that some of the tools have a suffix, when others
   282       don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
   283       for that by checking the tools without the suffix in case it can
   284       not find some of the tool.
   285 
   286 endif # CROSS_NATIVE || CANADIAN
   287 
   288 endmenu