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] Adding Fluxbox window manager
Date: Wed, 3 Aug 2011 09:56:32 +0200	[thread overview]
Message-ID: <20110803095632.72d84561@skate> (raw)
In-Reply-To: <CAAXf6LWyzvEKG_us4XJtM5T_CgCPHkUM9oSBMyf7KWXVqO3NYA@mail.gmail.com>

Le Wed, 3 Aug 2011 09:46:16 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :

> >> +FLUXBOX_VERSION:=1.3.1
> >> +FLUXBOX_SOURCE:=fluxbox-$(FLUXBOX_VERSION).tar.bz2
> >> +FLUXBOX_SITE:=http://$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/sourceforge/fluxbox/
> >
> > Please use = instead of :=.
> 
> Just curious: why do you recommend against := ?
> For example in the case of FLUXBOX_SOURCE, using := would avoid
> unnecessary expansions of $(FLUXBOX_VERSION), each time FLUXBOX_SOURCE
> is used.
> For FLUXBOX_SITE it depends on whether BR2_SOURCEFORGE_MIRROR is
> already defined or not, but I think it has, right?

Peter Korsgaard said:

""""
:= is only a performance advantage if variables are expensive to expand
(use) and are used more than once - E.G. stuff involving $(shell) and
similar, like the UPPERCASE macro we had calling tr.

= has a number of advantages though. As it only gets expanded at the
last possible moment you don't have to take care about variable
ordering, E.G. when you use a variable like LIBGLIB2_HOST_BINARY on
another package, whereas with := you do. This can also be interesting
when the variable contains $(shell) or other functions, as you might
only want to execute them if/when they are needed, and not right away
when the Makefiles are parsed.

I would prefer to use = by default, and only use := where it matters for
correctness or performance.
""""

See:

Subject: Re: [Buildroot] [PATCH 07/28] barebox: use = instead of := and re-indent
Date: Tue, 05 Jul 2011 23:04:58 +0200
Message-ID: <87sjqkv3ph.fsf@macbook.be.48ers.dk>

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-08-03  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 17:10 [Buildroot] [PATCH] Adding Fluxbox window manager Frederic Bassaler
2011-08-02 18:44 ` Thomas Petazzoni
2011-08-03  7:46   ` Thomas De Schampheleire
2011-08-03  7:56     ` Thomas Petazzoni [this message]
2011-08-03  8:03       ` 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=20110803095632.72d84561@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