staging/jow/include/target.mk, branch main

target/metadata: set OpenWrt One as the default menuconfig target/profile

2024-12-02T12:55:36Z

Signed-off-by: John Crispin

Revert "target,base-files: unify handling of procd-ujail"

2024-11-26T05:07:33Z

This reverts commit ac640718aa0ceae55969bb9e7e45d00bb7bc228a as it removes base-files package when KERNEL_NAMESPACES is deselected, as base-files depends on procd-ujail which needs KERNEL_NAMESPACES. Fixes: #17075 Link: https://github.com/openwrt/openwrt/pull/17081 Link: https://github.com/openwrt/openwrt/pull/17081 Signed-off-by: Petr Štetiar

target,base-files: unify handling of procd-ujail

2024-11-17T18:29:06Z

Remove the remaining special handling of procd-ujail in a same way as the rest of the packages was handled in the commit 4c65359af49b ("build: fix including busybox, procd and apk/opkg in imagebuilder"). Fixes: 44598c233dd9 ("build: remove broken dependency of metadata on toplevel .config variables") Signed-off-by: Petr Štetiar Link: https://github.com/openwrt/openwrt/pull/16986 Signed-off-by: Robert Marko

build: add comments to makefiles

2024-11-12T16:56:07Z

Add comments to build system makefile functions and variables to help developers in understanding build system internals and ease the development process. This patch adds some documentation examples with proposed doxygen-like syntax. Hopefully, this would start the discussion and result in generation of the makefile documentation guidelines. Signed-off-by: Sergey Matsievskiy Link: https://github.com/openwrt/openwrt/pull/16888 Signed-off-by: Christian Marangi

build: remove broken dependency of metadata on toplevel .config variables

2024-11-11T18:53:43Z

Instead of relying on .config symbols for metadata, alter the DEFAULT variable of affected packages. Fixes enabling opkg vs apk among others. Signed-off-by: Felix Fietkau

target.mk: init default configs if they are missing in the .config

2024-07-18T12:15:49Z

The config options that are enabled by default and where other default packages depends on should not only be set if there is no .config file, but also if the .config exists but the config option (e.g. CONFIG_SECCOMP) is missing in the file. This is relevant, for example, if you are working with .config templates and then want to complete the configuration using make defconfig. Signed-off-by: Martin Schiller

target.mk: further improve handling of default enabled SECCOMP

2024-07-18T12:15:49Z

The fix in commit 847fad476f3d ("target.mk: improve handling of default enabled SECCOMP") unfortunately does not work for targets where the ARCH variable is set in ./$(SUBTARGET)/target.mk. To get this working, the ./$(SUBTARGET)/target.mk must be included before the check. Fixes: 847fad476f3d ("target.mk: improve handling of default enabled SECCOMP") Signed-off-by: Martin Schiller

target.mk: fix arm architecture level detection

2024-07-03T11:09:47Z

Now kernel configs of armv6k CPUs don't include CONFIG_CPU_V6. So armv6k CPUs cannot be detected as arm_v6. Fix this by adding detection for CONFIG_CPU_V6K. Signed-off-by: Lu jicong Link: https://github.com/openwrt/openwrt/pull/15855 Signed-off-by: Christian Marangi

target.mk: improve handling of default enabled SECCOMP

2024-06-19T14:19:10Z

Handling default packages selection is really problematic and error prone. In all the changes, the SECCOMP config is enabled by default if supported by the target. This is problematic for the scenario of the first .config creation where this option will be enabled by default but the package default are already being parsed. This cause the reparsing of the default package on the next command and the "outdated config" error. To better handle this special case, add additiona logic to match the dependency in the config and check if CONFIG_SECCOMP should be enabled by default in the scenario where a .config needs to be init and doesn't exist. Signed-off-by: Christian Marangi

toplevel.mk: implement logic to invalidate targetinfo with some config

2024-06-11T21:58:16Z

Implement some logic to invalidate targetinfo files in tmp with the changing of some config. Some config might affect DEFAULT_PACKAGES list but DEFAULT_PACKAGES is only evaluated once. This cause the interesting scenario where someone install feeds packages, targetinfo is evaluated in tmp and then add some config like CONFIG_USE_APK. Using make defconfig will still select OPKG as default package as DEFAULT_PACKAGES in targetinfo has been already evaluated in the feeds install and is never updated. To handle this add some logic in toplevel.mk to cache the current state of these special config and wipe targetinfo when these change. This cause the targetinfo to be reevaluated and handle this REALLY corner case. Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi