staging/ynezz/Makefile, branch master

Revert "build: replace which with Bash command built-in"

2021-03-03T21:51:39Z

This reverts commit c7aec47e5e3a3ff7b5fdaa11cd1e62cae6746acb. The original commit replaces 'which' with 'command'. Sadly most of them are not equivalent and for 'which -a', there is no easy replacements that would not reimplement PATH parsing logic. Hence revert. Keeping a dependency on which is absolutely fine. Signed-off-by: Clemens Fruhwirth

Revert "build: use config.site generated by autoconf-lean, drop hardcoded sitefiles"

2021-03-02T11:35:45Z

This reverts commit f439e291304a93b982e912dc91b80ca950a594f3. Signed-off-by: Daniel Golle

build: use config.site generated by autoconf-lean, drop hardcoded sitefiles

2021-02-28T00:09:09Z

Signed-off-by: Felix Fietkau

build: use SPDX license tags

2021-02-05T13:54:47Z

The license folder is a core part of OpenWrt and all GPL-2.0 licensed. Use SPDX license tags to allow machines to check licenses. Signed-off-by: Paul Spooren [rebase, keep some Copyright lines, sharpen commit message] Signed-off-by: Adrian Schmutzler

build: use ccache -C for cleaning the cache

2021-01-07T01:31:18Z

This keeps the configuration, like the size of the cache, and the statistics intact. Move the removal of the cache directory to the distclean target, but only delete the .ccache directory inside of our build tree, as we should not mess with a user-configured external ccache directory this destructively. Signed-off-by: Sven Wegener

build: replace which with Bash command built-in

2021-01-04T18:32:25Z

`which` utility is not shipped by default for example on recent Arch Linux and then any steps relying on its presence fails, like for example following Python3 prereq build check: $ python3 --version Python 3.9.1 $ make /bin/sh: line 1: which: command not found /bin/sh: line 1: which: command not found /bin/sh: line 1: which: command not found ... Checking 'python3'... failed. ... Fix this by switching to Bash builtin `command` which should provide same functionality. Fixes: FS#3525 Signed-off-by: Petr Štetiar

build: use CCACHE_DIR for ccache directory

2021-01-01T23:31:11Z

It is being set by rules.mk with the same expression. Signed-off-by: Sven Wegener

build: improve ccache support

2020-07-11T13:19:53Z

Set CCACHE_DIR to $(TOPDIR)/.ccache and CCACHE_BASEDIR to $(TOPDIR). This allows to do clean and dirclean. Cache hit rate for test build after dirclean is ~65%. If CCACHE is enabled stats are printed out at the end of building process. CCACHE_DIR config variable allows to override default, which could be useful when sharing cache with many builds. cacheclean make target allows to clean the cache. Changes from v1: - remove ccache directory using CCACHE_DIR variable - remove ccache leftovers from sdk and toolchain make files - introduce CONFIG_CCACHE_DIR variable - introduce cacheclean make target Signed-off-by: Roman Yeryomin

build: refactor JSON info files to `profiles.json`

2020-04-03T10:17:45Z

JSON info files contain machine readable information of built profiles and resulting images. These files were added in commit 881ed09ee6e2 ("build: create JSON files containing image info"). They are useful for firmware wizards and script checking for reproducibility. Currently all JSON files are stored next to the built images, resulting in up to 168 individual files for the ath79/generic target. This patch refactors the JSON creation to store individual per image (not per profile) files in $(BUILD_DIR)/json_info_files and create an single overview file called `profiles.json` in the target directory. Storing per image files and not per profile solves the problem of parallel file writes. If a profiles sysupgrade and factory image are finished at the same time both processes would write to the same JSON file, resulting in randomly broken outputs. Some target like x86/64 do not use the image code yet, resulting in missing JSON files. If no JSON info files were created, no `profiles.json` files is created as it would be empty anyway. As before, this creation is enabled by default only if `BUILDBOT` is set. Tested via buildroot & ImageBuilder on ath79/generic, imx6 and x86/64. Signed-off-by: Paul Spooren [json_info_files dir handling in Make, if case refactoring] Signed-off-by: Petr Štetiar

build: clean menuconfig utility as part of dirclean

2020-03-10T20:44:30Z

When sharing a common build directory between different build platforms eg. macos v docker based linux v virtual machine, a 'make dirclean' isn't quite enough to clean all the platform related binaries. The 'conf' and 'mconf' aka 'make menuconfig/defconfig & friends' utilities remain. Clean those as part of 'dirclean' so they get rebuilt for the current platform on the next 'make' Signed-off-by: Kevin Darbyshire-Bryant