From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 3 v3] uclibc: update-config: preserve freshly configured settings
Date: Mon, 21 Jul 2014 22:17:55 +0200 [thread overview]
Message-ID: <20140721221755.4e0346f5@free-electrons.com> (raw)
In-Reply-To: <f8c110cf3b83a4e29146.1405709696@localhost>
Dear Thomas De Schampheleire,
On Fri, 18 Jul 2014 20:54:56 +0200, Thomas De Schampheleire wrote:
> diff -r 29ba03b43b12 -r f8c110cf3b83 package/uclibc/uclibc.mk
> --- a/package/uclibc/uclibc.mk Sun Jun 22 10:37:22 2014 +0200
> +++ b/package/uclibc/uclibc.mk Mon Jun 16 20:18:23 2014 +0200
> @@ -432,7 +432,6 @@
> endef
>
> define UCLIBC_CONFIGURE_CMDS
> - $(UCLIBC_FIXUP_DOT_CONFIG)
> $(MAKE1) -C $(UCLIBC_DIR) \
> $(UCLIBC_MAKE_FLAGS) \
> PREFIX=$(STAGING_DIR) \
> @@ -537,7 +536,11 @@
> $(UCLIBC_DIR)/.config: $(UCLIBC_CONFIG_FILE) | uclibc-patch
> $(INSTALL) -m 0644 $(UCLIBC_CONFIG_FILE) $(UCLIBC_DIR)/.config
>
> -$(UCLIBC_TARGET_CONFIGURE): $(UCLIBC_DIR)/.config
> +$(UCLIBC_DIR)/.stamp_config_fixup_done: $(UCLIBC_DIR)/.config
> + $(UCLIBC_FIXUP_DOT_CONFIG)
> + $(Q)touch $@
> +
> +$(UCLIBC_TARGET_CONFIGURE): $(UCLIBC_DIR)/.stamp_config_fixup_done
>
> uclibc-menuconfig: $(UCLIBC_DIR)/.config
> $(MAKE1) -C $(UCLIBC_DIR) \
> @@ -546,9 +549,10 @@
> DEVEL_PREFIX=/usr/ \
> RUNTIME_PREFIX=$(STAGING_DIR)/ \
> menuconfig
> - rm -f $(UCLIBC_DIR)/.stamp_{configured,built,target_installed,staging_installed}
> + rm -f $(UCLIBC_DIR)/.stamp_{config_fixup_done,configured,built}
> + rm -f $(UCLIBC_DIR)/.stamp_{target,staging}_installed
>
> -uclibc-update-config: $(UCLIBC_DIR)/.stamp_configured
> +uclibc-update-config: $(UCLIBC_DIR)/.stamp_config_fixup_done
> cp -f $(UCLIBC_DIR)/.config $(UCLIBC_CONFIG_FILE)
Is a separate stamp file actually needed here? This patch changes all
references to $(UCLIBC_DIR)/.config as dependencies to references to
$(UCLIBC_DIR)/.stamp_config_fixup_done as a dependency, and
$(UCLIBC_DIR)/.stamp_config_fixup_done is the only target left having a
dependency on $(UCLIBC_DIR)/.config. So what prevents from doing:
$(UCLIBC_DIR)/.config: $(UCLIBC_CONFIG_FILE) | uclibc-patch
$(INSTALL) -m 0644 $(UCLIBC_CONFIG_FILE) $(UCLIBC_DIR)/.config
$(UCLIBC_FIXUP_DOT_CONFIG)
?
I'm probably missing one use case, but I find
this .stamp_config_fixup_done stamp file not so nice, so I'd like to
really understand why it's needed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-21 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 18:54 [Buildroot] [PATCH 0 of 3 v3] uclibc: fix handling of configuration file Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 1 of 3 v3] uclibc: rename SETUP_DOT_CONFIG to FIXUP_DOT_CONFIG Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 2 of 3 v3] uclibc: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 3 of 3 v3] uclibc: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-07-21 20:17 ` Thomas Petazzoni [this message]
2014-07-22 11:11 ` Thomas De Schampheleire
2014-07-22 18:24 ` Thomas De Schampheleire
2014-07-26 18:19 ` Thomas De Schampheleire
2014-07-29 21:48 ` [Buildroot] [PATCH 0 of 3 v3] uclibc: fix handling of configuration file Thomas Petazzoni
2014-07-30 5:21 ` Thomas De Schampheleire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140721221755.4e0346f5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox