From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: question about order of processing SRC_URI items
Date: Thu, 21 Apr 2016 09:56:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1604210951380.11134@localhost.localdomain> (raw)
In-Reply-To: <1461244406.31320.117.camel@linuxfoundation.org>
On Thu, 21 Apr 2016, Richard Purdie wrote:
> In general we should try and use += if possible as its simpler and
> easier to understand what it does.
regarding "_append +=", there are only two files left in oe-core
that i will let someone else deal with if they want. first:
meta/recipes-extended/images/core-image-kernel-dev.bb:
IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"
and there's this weirdness in meta/lib/oeqa/selftest/layerappend.py:
... snip ...
addtask build
"""
append = """
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append = " file://appendtest.txt"
sysroot_stage_all_append() {
install -m 644 ${WORKDIR}/appendtest.txt ${SYSROOT_DESTDIR}/
}
"""
append2 = """
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append += "file://appendtest.txt"
not quite sure what's going on there with those two variations of
assignment to SRC_URI, so i'm just going to leave it alone.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2016-04-21 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:19 question about order of processing SRC_URI items Robert P. J. Day
2016-04-21 13:13 ` Richard Purdie
2016-04-21 13:39 ` Robert P. J. Day
2016-04-21 13:56 ` Robert P. J. Day [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=alpine.LFD.2.20.1604210951380.11134@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox