Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] qt: add font license information
Date: Sat, 27 Feb 2016 23:23:57 +0100	[thread overview]
Message-ID: <56D221FD.1020602@mind.be> (raw)
In-Reply-To: <20160227220053.6ddafcc6@gmx.net>

On 02/27/16 22:00, Peter Seiderer wrote:
> Hello Danomi,
> 
> On Sat, 27 Feb 2016 11:38:39 -0500, Danomi Manchego <danomimanchego123@gmail.com> wrote:
> 
>> > Peter S.,
>> > 
>> > On Thu, Feb 25, 2016 at 5:34 PM, Peter Seiderer <ps.report@gmx.net> wrote:
>>> > > With this implementation, the different licenses will be separated with
>>> > > <space><comma>. This is not nice, but to avoid it a pretty ugly construct
>>> > > is needed:
>>> > >
>>> > > QT_LICENSE = $(shell echo $(QT_LICENSE_BITS) | sed 's% , %, %g')
>>> > >
>>> > > Since the <space><comma> is just a minor nuisance, we're not going to that kind
>>> > > of complexity.
>>> > >
>> > 
>> > The <space><comma> can be avoided during variable construction by doing this:
>> > 
>> > QT_LICENSE := BlahBlah
>> > 
>> > ifeq ...
>> > QT_LICENSE:=$(QT_LICENSE), MoreBlahBlah
>> > 
>> > If you don't mind the X:=$(X) part, that is.  IIRC, buildroot did a
>> > pass not long ago removing := from assignments that didn't actually
>> > need it.
>> > 
> Thanks for the tip, tried it and works for me ;-), but [1] states:
> 
>   Simply expanded variables are defined by lines using ?:=? or ?::=? (see Setting
>   Variables). Both forms are equivalent in GNU make; however only the ?::=? form
>   is described by the POSIX standard (support for ?::=? was added to the POSIX
>   standard in 2012, so older versions of make won?t accept this form either). 
> 
> Maybe this was the reason to avoid it in buildroot?

 Not at all - we use loads of GNU make specific things, like functions.

 There is no big reason to avoid :=, only for consistency we prefer to use =
everywhere. So in this case it would be OK to use :=. Note however that there
should be spaces around it (any whitespace after = will be stripped).

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2016-02-27 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 22:34 [Buildroot] [PATCH v3] qt: add font license information Peter Seiderer
2016-02-27  0:00 ` Arnout Vandecappelle
2016-02-27 10:57 ` Peter Korsgaard
2016-02-27 16:38 ` Danomi Manchego
2016-02-27 21:00   ` Peter Seiderer
2016-02-27 22:23     ` Arnout Vandecappelle [this message]

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=56D221FD.1020602@mind.be \
    --to=arnout@mind.be \
    --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