config/backend.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1877 b579a5cb53d1
child 2484 d1a8c2ae7946
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@1869
     1
# Options specific to crosstool-NG acting as a backend
yann@121
     2
yann@1842
     3
config IS_A_BACKEND
yann@1842
     4
    string
yann@1842
     5
    option env="CT_IS_A_BACKEND"
yann@1842
     6
yann@1842
     7
config BACKEND
yann@1842
     8
    bool
yann@1842
     9
    default y if IS_A_BACKEND =  "y" || IS_A_BACKEND =  "Y"
yann@1842
    10
    default n if IS_A_BACKEND != "y" && IS_A_BACKEND != "Y"
yann@1842
    11
yann@1868
    12
config BACKEND_ARCH
yann@1868
    13
    string
yann@1868
    14
    option env="CT_BACKEND_ARCH"
yann@1868
    15
yann@1868
    16
config BACKEND_KERNEL
yann@1868
    17
    string
yann@1868
    18
    option env="CT_BACKEND_KERNEL"
yann@1878
    19
yann@1878
    20
config BACKEND_LIBC
yann@1878
    21
    string
yann@1878
    22
    option env="CT_BACKEND_LIBC"