staging/hauke/include/u-boot.mk, branch v23.05.0

u-boot.mk: add support for config customization

2023-06-13T12:15:21Z

Make it possible to easily customize U-Boot config options via new `UBOOT_CUSTOMIZE_CONFIG` variable, so we don't need to patch config files or override config step with shell hackery. This generic approach uses `config` CLI to tweak the .config as needed, for example: UBOOT_CUSTOMIZE_CONFIG := \ --enable CMD_EFIDEBUG \ --enable CMD_BOOTMENU \ --enable AUTOBOOT \ --enable AUTOBOOT_MENU_SHOW \ --disable AUTOBOOT_KEYED \ --disable AUTOBOOT_USE_MENUKEY \ --disable BOOTMENU_DISABLE_UBOOT_CONSOLE \ --set-val BOOTDELAY 2 Signed-off-by: Petr Štetiar (cherry picked from commit 186b97590b9b2f47abc535c9df0687e00e60f78e)

u-boot.mk: add LOCALVERSION (explicitly specify OpenWrt build)

2022-02-28T22:54:52Z

For debugging purposes, we need to know if users are using modified U-boot versions or not. Currently, the U-boot version is somehow stripped. This is a little bit problematic when there are backported/wip/to-upstream patches. To make it more confusing, there was (before this commit) two U-boot versioning. U-boot compiled by OpenWrt build bots are missing ``Build:`` This is also the case when the U-boot is compiled locally. Example: ``` U-Boot SPL 2022.01 (Jan 27 2022 - 00:24:34 +0000) U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000) ``` On the other hand, if you run full build, you can at least see, where it was compiled. Notice added ``Build:``. Example: ``` U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000), Build: jenkins-turris-os-packages-burstlab-omnia-216 ``` In both cases, it is not clear to U-boot developers if it is an unmodified build. This is also caused that there is a missing ``.git`` file from U-boot folder, and so there is no history. It leads to that it can not contain suffix ``-dirty`` (uncommitted modifications) or even something else like number of commits, etc. [1] When U-boot is compiled as it should be, the version should look like this: ``U-Boot 2022.04-rc1-01173-g278195ea1f (Feb 11 2022 - 14:46:50 +0100)`` The date is not changed daily when there are new OpenWrt builds. This commit adds OpenWrt specific version, which could be verified by using strings. ``` $ strings bin/targets/mvebu/cortexa9/u-boot-omnia/u-boot-spl.kwb | grep -E "OpenWrt*" U-Boot SPL 2022.01-OpenWrt-r18942+54-cbfce92367 (Feb 21 2022 - 13:17:34 +0000) arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r18942+54-cbfce92367) 11.2.0 2022.01-OpenWrt-r18942+54-cbfce92367 U-Boot 2022.01-OpenWrt-r18942+54-cbfce92367 (Feb 21 2022 - 13:17:34 +0000) ``` [1] https://u-boot.readthedocs.io/en/latest/develop/version.html Reported-by: Pali Rohár Suggested-by: Karel Kočí Signed-off-by: Josef Schlehofer

u-boot.mk: always link host libraries static

2021-10-24T16:00:49Z

Host libraries are only build static, so let's pass --static to pkg-config globally and remove the then unnecessary patches doing exactly that individually. Signed-off-by: Andre Heider

u-boot.mk: fix pkg-config usage

2021-10-24T16:00:49Z

Using Host/Exports doesn't work as intended, explicitly add the required vars so that u-boot finds the required libraries when building its tools. Signed-off-by: Andre Heider

u-boot: support verbose build

2021-06-12T08:46:39Z

Signed-off-by: Felix Fietkau

u-boot.mk: switch download to https

2020-04-26T19:20:47Z

ftp can cause problems on some networks switch primary download location to https and add another mirror Signed-off-by: Lucian Cristian

u-boot.mk: use openwrt url instead of lede project

2019-08-18T15:14:13Z

The LEDE URL is automatically redirected to the OpenWRT one, returning an HTTP 301 code (Moved Permanently). Also, use https, as indicated by the redirect. Signed-off-by: Luis Araneda

u-boot.mk: Fix building of recent U-Boot sources

2019-01-26T20:46:32Z

This patch fixes following error with U-Boot 2019.01 on imx6: In file included from tools/lib/crc16.c:1:0: ./tools/../lib/crc16.c: In function 'crc16_ccitt': ./tools/../lib/crc16.c:70:2: error: 'for' loop initial declarations are only allowed in C99 mode for (int i = 0; i < len; i++) ^ ./tools/../lib/crc16.c:70:2: note: use option -std=c99 or -std=gnu99 to compile your code Code was introduced in the upstream v2019.01-rc1-154-g51c2345: commit 51c2345bd24837f9f67f16268da6dc71573f1325 Author: Philipp Tomsich Date: Sun Nov 25 19:22:19 2018 +0100 Roll CRC16-CCITT into the hash infrastructure Upstream has added -std=gnu11 host flag in v2018.07-rc2-1-gfa89399: commit fa893990e9b53425af5f5059e04a2bffde91ccf9 Author: Tom Rini Date: Tue Jun 19 23:53:54 2018 -0400 Makefile: Ensure we build with -std=gnu11 Build tested on imx6: apalis, mx6sabresd, nitrogen6dl, nitrogen6dl2g, nitrogen6q, nitrogen6q2g, nitrogen6s, nitrogen6s1g, wandboard Run tested: apalis (pending PR #1595) Signed-off-by: Petr Štetiar

u-boot.mk: add HOST_LDFLAGS to UBOOT_MAKE_FLAGS

2018-02-10T19:52:31Z

This will make sure that the build system's paths for linking are available. This is needed mostly for linking with tools/libressl. Signed-off-by: Alexandru Ardelean

u-boot,at91bootstrap: fix incorrect HOSTCPPFLAGS variable

2018-02-10T19:52:31Z

This would should up as `$$(HOSTCPPFLAGS)` in the host CFLAGS. ``` make --jobserver-fds=3,4 -j -C /build_dir/target-arm_cortex-a8+vfpv3_musl_eabi/u-boot-A10-OLinuXino-Lime/u-boot-2017.07 CROSS_COMPILE=arm-openwrt-linux-muslgnueabi- DTC="/build_dir/target-arm_cortex-a8+vfpv3_musl_eabi/linux-sunxi_cortexa8/linux-4.9.76/scripts/dtc/dtc" HOSTCC="gcc" HOSTCFLAGS='-O2 -I/staging_dir/host/include -I/staging_dir/host/usr/include -I/staging_dir/hostpkg/include -I/staging_dir/target-arm_cortex-a8+vfpv3_musl_eabi/host/include $$(HOSTCPPFLAGS)' HOSTLDFLAGS="" BL31=/staging_dir/target-arm_cortex-a8+vfpv3_musl_eabi/image/bl31.bin ``` And then it would complain with: ``` /bin/sh: 1: HOSTCPPFLAGS: not found ``` Also, HOSTCPPFLAGS does not exist. The correct var is HOST_CPPFLAGS. Signed-off-by: Alexandru Ardelean