Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: target-purgelocales: add dependencies
Date: Mon, 28 Apr 2014 18:10:38 +0200	[thread overview]
Message-ID: <20140428181038.6d83619a@skate> (raw)
In-Reply-To: <87tx9dx0c0.fsf@dell.be.48ers.dk>

Peter, Arnout,

On Mon, 28 Apr 2014 11:36:15 +0200, Peter Korsgaard wrote:

>  >  My personal preference is to have a single rule (e.g. target-finalize)
>  > that performs everything that is post-targets and pre-rootfs. There isn't
>  > much that needs to be done so parallelisation doesn't make sense. And I
>  > think it's much easier to understand which steps are executed and in
>  > which order if they are all put together in a single rule rather than
>  > spread out over several.
> 
>  >  To make things more readable, we can put the commands into separate
>  > variables. For instance:
> 
>  > define TARGET_PURGE_LOCALES
>  > 	rm -f $(LOCALE_WHITELIST)
>  > 	...
>  > endef
> 
>  > define TARGET_PURGE_DEVFILES
>  > 	rm -rf $(TARGET_DIR)/usr/include ...
>  > ...
>  > endef
> 
>  > ifneq ($(BR2_PACKAGE_GDB),y)
>  > define TARGET_PURGE_GDB
>  >         rm -rf $(TARGET_DIR)/usr/share/gdb
>  > endef
>  > endif
> 
>  > target-finalize: $(TARGETS)
>  > 	$(TARGET_PURGE_LOCALES)
>  > 	$(TARGET_PURGE_DEVFILES)
>  > 	$(TARGET_PURGE_GDB)
>  > 	$(TARGET_PURGE_DOC)
>  > ...
> 
> Yes, that looks nice and clear to me too.

Yes, agreed, this looks a lot nicer than a long chain of targets that
simply depend on each other to avoid any parallelization.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-04-28 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 16:24 [Buildroot] [PATCH] Makefile: target-purgelocales: add dependencies Fabio Porcedda
2014-04-24 16:41 ` Thomas Petazzoni
2014-04-25 21:50   ` Fabio Porcedda
2014-04-28  5:49     ` Arnout Vandecappelle
2014-04-28  7:58       ` Fabio Porcedda
2014-04-28 10:30         ` Arnout Vandecappelle
2014-04-28 10:32           ` Fabio Porcedda
2014-04-28  9:36       ` Peter Korsgaard
2014-04-28 16:10         ` Thomas Petazzoni [this message]
2014-06-11  9:24           ` Fabio Porcedda

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=20140428181038.6d83619a@skate \
    --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