staging/pepe2k/include/scan.mk, branch v22.03.3

build: fix find warning with SCAN_EXTRA

2022-06-07T20:28:59Z

If you change SCAN_EXTRA variable with "-path target/linux/xxxx" in include/toplevel.mk for speed up scan, find will warn with: find: warning: you have specified the global option -maxdepth after the argument -path, but global options are not positional, i.e., -maxdepth affects tests specified before it as well as those specified after it. Please specify global options before other arguments. The find option -mindepth -maxdepth are global options and must be before any path option. Change order of $(SCAN_EXTRA) after -mindepth and -maxdepth to fix this. Signed-off-by: Leo Chung [capitalize Description, Author and Sob and minor description tweak] Signed-off-by: Christian 'Ansuel' Marangi (cherry picked from commit eb787b5b9d8d45f3678b58eaa158bb4fa28d4418)

build: introduce $(MKHASH)

2021-05-13T13:13:15Z

Before this commit, it was assumed that mkhash is in the PATH. While this was fine for the normal build workflow, this led to some issues if make TOPDIR="$(pwd)" -C "$pkgdir" compile was called manually. In most of the cases, I just saw warnings like this: make: Entering directory '/home/.../package/gluon-status-page' bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found [...] While these were only warnings and the package still compiled sucessfully, I also observed that some package even fail to build because of this. After applying this commit, the variable $(MKHASH) is introduced. This variable points to $(STAGING_DIR_HOST)/bin/mkhash, which is always the correct path. Signed-off-by: Leonardo Mörlein

build: have scripts/feeds honor all toplevel .mk-files of a feed

2019-10-27T13:32:13Z

The luci and freifunk feed having a common Makefile included by the individual packages. Currently a change to this file will be ignored when running "scripts/feeds update". When we are updating for a feed, add a dependency for all .mk files in the root of it. Signed-off-by: Sven Roederer

build: Fix print without color

2019-02-17T18:30:34Z

The original patch removed the printing completely, just remove the color. Fixes: eabc1ddc4541 ("build: Honour NO_COLOR in include/scan.mk") Signed-off-by: Hauke Mehrtens

build: Honour NO_COLOR in include/scan.mk

2019-02-17T18:22:04Z

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. Hi all: This is my first OpenWrt patch. I am a clean, pure newbie! 8-) Honour NO_COLOR in Makefile function 'progress' in include/scan.mk, in the same way that include/verbose.mk does. Signed-off-by: R. Diez

build: fix target metadata scan dependencies

2018-07-02T12:27:06Z

Move SCAN_DEPS to scan.mk to eliminate redundancy with scripts/feeds Add image/*.mk to SCAN_DEPS for targets to pick up newly added devices Signed-off-by: Felix Fietkau

build: get rid of host.mk

2017-02-26T12:31:44Z

Defined required host related variables in toplevel.mk instead Signed-off-by: Felix Fietkau

build: get rid of FIND_L from host.mk

2017-02-26T12:31:44Z

This was added for Mac OS X many years ago, but recent versions also support find -L Signed-off-by: Felix Fietkau

build: scan.mk: consider KernelPackage pattern as well

2017-01-10T15:26:55Z

The removal of the ".+Package" pattern in scan.mk also caused the build system to skip over Makefiles defining only kmods. Adjust the grep pattern to consider packages with "call KernelPackage" signatures as well. Signed-off-by: Jo-Philipp Wich

build: scan.mk: remove overlay broad grep pattern

2017-01-10T14:16:28Z

Commit af0b91c "allow scan.mk to find python packages introduced in [8639]" added some special casing to scan.mk to accomodate some nonstandard python packages. Nowadays this pattern is not needed anymore and produces false positives when using the LEDE source repository as feed within the SDK since the metadata scanning wrongly picks up target/imagebuilder/Makefile as package, leading to an "ERROR: please fix feeds/base/target/imagebuilder/Makefile" message. Remove the now uneeded pattern to fix such stray errors during metadata scanning. Signed-off-by: Jo-Philipp Wich