config/backend.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Mar 15 23:18:37 2011 +0100 (2011-03-15)
changeset 2340 580f427595bc
parent 1877 b579a5cb53d1
child 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts: allow logging of commands with variables

In a lot of places, we need to call some commands with specific
variable settings, a-la:
var1=val1 var2=val2 /foo/bar/buz opt1 opt2

Unfortunately, we currently can not log the variable settings.

Enhance CT_DoExecLog with a crude heuristic that works pretty well
and that can also log setting variables.

Reported-by: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
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"