aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Angelo Compagnucci <angelo.compagnucci@gmail.com>2019-11-26 14:24:58 +0100
committerGravatar Thomas Petazzoni <thomas.petazzoni@bootlin.com>2019-12-05 21:32:58 +0100
commitd1f1947af12fc47933c7ea8fa90fc40d423affd2 (patch)
tree72e9ae6fb0be4a8a46b8a263eb1548e96d8a9384
parenta991a6c83474e888fd7ed4bf6fc68dd8e180d916 (diff)
downloadbuildroot-d1f1947af12fc47933c7ea8fa90fc40d423affd2.tar.gz
buildroot-d1f1947af12fc47933c7ea8fa90fc40d423affd2.tar.bz2
package/pkg-kconfig: fix reconfigure for kconfig packages
Commit 4b81badbcc0b25678ac6627548160702731cf393 Currently, calling foo-reconfigure for a kconfig-based package will not re-trigger the configuration (kconfig-wise) step for the package. was supposed to solve this problem and lately we had Commit 05fea6e4a60a38a797d9bacbf318a2cd7dbd435f infra/pkg-kconfig: do not rely on package's .config as a timestamp that introduced the .stamp_dotconfig file. For this reason, to trigger a kconfig package reconfigure is now necessary to remove the .stamp_dotconfig file. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
-rw-r--r--package/pkg-kconfig.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk
index e435b95bcf..e2d52ee8ed 100644
--- a/package/pkg-kconfig.mk
+++ b/package/pkg-kconfig.mk
@@ -176,7 +176,7 @@ $$($(2)_TARGET_CONFIGURE): $$($(2)_DIR)/.stamp_kconfig_fixup_done
$(1)-clean-for-reconfigure: $(1)-clean-kconfig-for-reconfigure
$(1)-clean-kconfig-for-reconfigure:
- rm -f $$($(2)_DIR)/.stamp_kconfig_fixup_done
+ rm -f $$($(2)_DIR)/$$($(2)_KCONFIG_STAMP_DOTCONFIG)
# Only enable the foo-*config targets when the package is actually enabled.
# Note: the variable $(2)_KCONFIG_VAR is not related to the kconfig