From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 4/4] gcc: replace unconditional SRC_URI_append with SRC_URI +=
Date: Fri, 07 Jan 2011 13:39:06 +0100 [thread overview]
Message-ID: <4D27096A.2050605@opendreambox.org> (raw)
In-Reply-To: <1294393961.3699.5.camel@mattotaupa>
On 01/07/2011 10:52 AM, Paul Menzel wrote:
> Am Donnerstag, den 06.01.2011, 12:48 +0000 schrieb Andreas Oberritter:
>
> What do you mean by »unconditional SRC_URI_append«? I searched through
> the documentation and could not find the word.
Unconditional, because it doesn't contain an override like e.g.
SRC_URI_append_beagleboard does.
> I always thought
> `SRC_URI_append =` and `SRC_URI +=` is the same and if I am not mistaken
> the manual says the same [1].
>
> Do I understand your patch correctly, that when `_append` was used in
> the recipe in some places, the space was missing and that you chose to
> replace it by `+=` for consistency?
Yes. I think that += is easier to use and less error-prone.
- As Koen already pointed out, it adds whitespace automatically, so in
whitespace separated lists like SRC_URI you don't have to care.
- You can use multiple statements in a recipe.
SRC_URI += "foo"
SRC_URI += "bar"
vs.
SRC_URI_append = " foo"
SRC_URI_append = " bar"
The latter wouldn't work.
In the case of gcc, I modified SRC_URI in some inc file resulting in
"... file://my.patchfile://fortran-cross-compile-hack.patch ...".
> [1] http://docs.openembedded.org/usermanual/usermanual.html#recipes_syntax
SRC_URI_append = "file://fixup.patch" is probably a bad example.
Regards,
Andreas
next prev parent reply other threads:[~2011-01-07 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 12:48 [PATCH 1/4] python-wifi: add recipe for version 0.5.0 Andreas Oberritter
2011-01-06 12:48 ` [PATCH 2/4] python-wifi: remove version 0.3.1 Andreas Oberritter
2011-01-06 13:07 ` Dr. Michael Lauer
2011-01-06 14:18 ` Frans Meulenbroeks
2011-01-06 14:30 ` Martin Jansa
2011-01-06 12:48 ` [PATCH 3/4] unpack.py: add SRC_URI parameter unpack=<bool> (default: true) Andreas Oberritter
2011-01-11 20:31 ` Andreas Oberritter
2011-01-11 21:48 ` Bernhard Reutner-Fischer
2011-01-11 22:19 ` Andreas Oberritter
2011-01-12 8:23 ` Bernhard Reutner-Fischer
2011-01-06 12:48 ` [PATCH 4/4] gcc: replace unconditional SRC_URI_append with SRC_URI += Andreas Oberritter
2011-01-06 22:40 ` Khem Raj
2011-01-07 9:52 ` Paul Menzel
2011-01-07 12:02 ` Koen Kooi
2011-01-07 12:39 ` Andreas Oberritter [this message]
2011-01-06 13:06 ` [PATCH 1/4] python-wifi: add recipe for version 0.5.0 Dr. Michael Lauer
2011-01-06 14:19 ` Frans Meulenbroeks
2011-01-06 14:30 ` Martin Jansa
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=4D27096A.2050605@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.