aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Angelo Compagnucci <angelo.compagnucci@gmail.com>2019-11-26 14:24:58 +0100
committerGravatar Peter Korsgaard <peter@korsgaard.com>2019-12-07 11:55:58 +0100
commitdfbaa5bc62ea630a1b8f922a06c9f9c2ebde8fde (patch)
treea99afcdb147f09b0d64ee044242f552b246cc6a9
parenta0ed87e197cb4888705cce4d36c09e48e2ab6276 (diff)
downloadbuildroot-dfbaa5bc62ea630a1b8f922a06c9f9c2ebde8fde.tar.gz
buildroot-dfbaa5bc62ea630a1b8f922a06c9f9c2ebde8fde.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> (cherry picked from commit d1f1947af12fc47933c7ea8fa90fc40d423affd2) Signed-off-by: Peter Korsgaard <peter@korsgaard.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 86d7c14fdb..f1931b87c6 100644
--- a/package/pkg-kconfig.mk
+++ b/package/pkg-kconfig.mk
@@ -175,7 +175,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