From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: "SRC_URI = file:///..." versus "externalsrc"?
Date: Wed, 1 Sep 2021 05:12:18 -0400 (EDT) [thread overview]
Message-ID: <a08e3ed-e66c-e973-fb43-8ca9c5fe9aa5@crashcourse.ca> (raw)
colleague asked me yesterday about the fundamental difference
between using SRC_URI to point at a local source tree to build, versus
inheriting externalsrc, and when to use each.
from what i read, there's no serious difference as, by default, both
techniques copy the source tree under WORKDIR -- the major difference
is that externalsrc can be configured to build in the source directory
via EXTERNALSRC_BUILD, which is something i would discourage anyway.
apart from that, is there an argument for one over the other
depending on the circumstances?
rday
reply other threads:[~2021-09-01 9:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a08e3ed-e66c-e973-fb43-8ca9c5fe9aa5@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox