systemd/tools/meson-apply-m4.sh

#!/bin/bash
# SPDX-License-Identifier: LGPL-2.1-or-later
set -eu

CONFIG="${1:?Missing path to config.h}"
TARGET="${2:?Missing target m4 file}"

if [ ! -f "$CONFIG" ]; then
    echo "$CONFIG not found."
    exit 2
fi

if [ ! -f "$TARGET" ]; then
    echo "$TARGET not found."
    exit 3
fi

DEFINES=()
mapfile -t DEFINES < <(awk '$1 == "#define" && $3 == "1" { printf "-D%s\n", $2 }' "$CONFIG")

m4 -P "${DEFINES[@]}" "$TARGET"
tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`#!/bin/bash`
tree-wide: add spdx header on all scripts and helpers Even though many of those scripts are very simple, it is easier to include the header than to try to say whether each of those files is trivial enough not to require one. 2021-01-27 15:37:10 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
meson: generate m4 preprocessor from config.h (#8914) 2018-05-07 12:17:35 +03:00			`set -eu`

tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`CONFIG="${1:?Missing path to config.h}"`
			`TARGET="${2:?Missing target m4 file}"`
meson: generate m4 preprocessor from config.h (#8914) 2018-05-07 12:17:35 +03:00
tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`if [ ! -f "$CONFIG" ]; then`
scripts: use 4 space indentation We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes. 2019-04-04 15:10:42 +03:00			`echo "$CONFIG not found."`
			`exit 2`
meson: generate m4 preprocessor from config.h (#8914) 2018-05-07 12:17:35 +03:00			`fi`

tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`if [ ! -f "$TARGET" ]; then`
scripts: use 4 space indentation We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes. 2019-04-04 15:10:42 +03:00			`echo "$TARGET not found."`
			`exit 3`
meson: generate m4 preprocessor from config.h (#8914) 2018-05-07 12:17:35 +03:00			`fi`

tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`DEFINES=()`
			`mapfile -t DEFINES < <(awk '$1 == "#define" && $3 == "1" { printf "-D%s\n", $2 }' "$CONFIG")`
meson: generate m4 preprocessor from config.h (#8914) 2018-05-07 12:17:35 +03:00
tools: shellcheck-ify most of the tool scripts 2021-04-20 14:02:02 +03:00			`m4 -P "${DEFINES[@]}" "$TARGET"`