0eab62b9cf
Upstream reimplemented KCONFIG_STRICT, just calling it KCONFIG_WERROR. Therefore, adapt our build system and documentation. Upstream is less strict at this time, but there's a proposed patch that got imported. TEST=`util/abuild/abuild -C` output (config.h and config.build) remains the same. Also, the failure type fixed in https://review.coreboot.org/c/coreboot/+/11272 can be detected, which I tested by manually breaking our Kconfig in a similar way. Change-Id: I322fb08a2f7308b93cff71a5dd4136f1a998773b Signed-off-by: Patrick Georgi <patrick@coreboot.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/79259 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Martin L Roth <gaumless@gmail.com> Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de>
40 lines
1,011 B
Bash
Executable file
40 lines
1,011 B
Bash
Executable file
#!/bin/sh
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
cflags=$1
|
|
libs=$2
|
|
bin=$3
|
|
|
|
PKG5="Qt5Core Qt5Gui Qt5Widgets"
|
|
PKG6="Qt6Core Qt6Gui Qt6Widgets"
|
|
|
|
if [ -z "$(command -v ${HOSTPKG_CONFIG})" ]; then
|
|
echo >&2 "*"
|
|
echo >&2 "* 'make xconfig' requires '${HOSTPKG_CONFIG}'. Please install it."
|
|
echo >&2 "*"
|
|
exit 1
|
|
fi
|
|
|
|
if ${HOSTPKG_CONFIG} --exists $PKG6; then
|
|
${HOSTPKG_CONFIG} --cflags ${PKG6} > ${cflags}
|
|
# Qt6 requires C++17.
|
|
echo -std=c++17 >> ${cflags}
|
|
${HOSTPKG_CONFIG} --libs ${PKG6} > ${libs}
|
|
${HOSTPKG_CONFIG} --variable=libexecdir Qt6Core > ${bin}
|
|
exit 0
|
|
fi
|
|
|
|
if ${HOSTPKG_CONFIG} --exists $PKG5; then
|
|
${HOSTPKG_CONFIG} --cflags ${PKG5} > ${cflags}
|
|
${HOSTPKG_CONFIG} --libs ${PKG5} > ${libs}
|
|
${HOSTPKG_CONFIG} --variable=host_bins Qt5Core > ${bin}
|
|
exit 0
|
|
fi
|
|
|
|
echo >&2 "*"
|
|
echo >&2 "* Could not find Qt6 or Qt5 via ${HOSTPKG_CONFIG}."
|
|
echo >&2 "* Please install Qt6 or Qt5 and make sure it's in PKG_CONFIG_PATH"
|
|
echo >&2 "* You need $PKG6 for Qt6"
|
|
echo >&2 "* You need $PKG5 for Qt5"
|
|
echo >&2 "*"
|
|
exit 1
|