From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 20 Nov 2018 17:35:22 +0100 Subject: [Buildroot] [PATCH next v5 9/9] package/pkg-kconfig: handle KCONFIG_DEPENDENCIES with per-package folders In-Reply-To: <20181120163522.4281-1-thomas.petazzoni@bootlin.com> References: <20181120163522.4281-1-thomas.petazzoni@bootlin.com> Message-ID: <20181120163522.4281-10-thomas.petazzoni@bootlin.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net The pkg-kconfig infrastructure hijacks the regular chain of build steps to insert its own step to prepare the configuration of kconfig packages. This additional step may have dependencies of its own, such as host-flex, host-bison or toolchain. In the context of per-package folder support, those dependencies must be copied to the per-package folder of the current package prior to doing the config preparation. This commit implements this logic by adding a call to prepare-per-package-folder at the right spot. Reported-by: Andreas Naumann Signed-off-by: Thomas Petazzoni --- package/pkg-kconfig.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk index d6c95b897e..bf43632adc 100644 --- a/package/pkg-kconfig.mk +++ b/package/pkg-kconfig.mk @@ -113,6 +113,7 @@ endef # Since the file could be a defconfig file it needs to be expanded to a # full .config first. $$($(2)_DIR)/$$($(2)_KCONFIG_DOTCONFIG): $$($(2)_KCONFIG_FILE) $$($(2)_KCONFIG_FRAGMENT_FILES) + $$(call prepare-per-package-folder,$$($(2)_KCONFIG_DEPENDENCIES)) $$(Q)$$(if $$($(2)_KCONFIG_DEFCONFIG), \ $$($(2)_KCONFIG_MAKE) $$($(2)_KCONFIG_DEFCONFIG), \ $$(INSTALL) -m 0644 -D $$($(2)_KCONFIG_FILE) $$(@)) -- 2.19.1