Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/backend.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 1877 b579a5cb53d1
child 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # Options specific to crosstool-NG acting as a backend

     2 

     3 config IS_A_BACKEND

     4     string

     5     option env="CT_IS_A_BACKEND"

     6 

     7 config BACKEND

     8     bool

     9     default y if IS_A_BACKEND =  "y" || IS_A_BACKEND =  "Y"

    10     default n if IS_A_BACKEND != "y" && IS_A_BACKEND != "Y"

    11 

    12 config BACKEND_ARCH

    13     string

    14     option env="CT_BACKEND_ARCH"

    15 

    16 config BACKEND_KERNEL

    17     string

    18     option env="CT_BACKEND_KERNEL"

    19 

    20 config BACKEND_LIBC

    21     string

    22     option env="CT_BACKEND_LIBC"
crosstool-ng