From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: couple questions on PACKAGECONFIG (for improving docs)
Date: Mon, 6 Apr 2020 12:05:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2004061153450.16686@localhost.localdomain> (raw)
wanted to tweak the ref manual entry for PACKAGECONFIG, so a couple
issues. first, the ref manual entry:
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGECONFIG
says nothing about the possible *sixth* entry, described in
base.bbclass as "foo_conflict_packageconfig", so i can add that but
i'm open to proper wording since i'd probably screw it up.
(i'd add an actual example from poky/ demonstrating this, such as:
meta/recipes-support/curl/curl_7.69.1.bb:PACKAGECONFIG[threaded-resolver]
= "--enable-threaded-resolver,--disable-threaded-resolver,,,,ares"
i'd be tempted to show some of the simpler variations of
PACKAGECONFIG, such as (if i read it correctly) being equivalent to
simply adding RDEPENDS values (right?):
meta/recipes-support/boost/boost.inc:PACKAGECONFIG[graph_parallel] =
",,,boost-mpi mpich"
finally, i'd toss in explaining this, which might confuse people:
meta/recipes-multimedia/pulseaudio/pulseaudio.inc:PACKAGECONFIG[autospawn-for-root]
= ",,,"
i'm betting some developers might wonder what that is all about and,
for every example i've seen for that, it involves *something*
explicitly checking for that config setting somewhere in the recipe,
as in the case above:
do_compile_append () {
if ${@bb.utils.contains('PACKAGECONFIG', 'autospawn-for-root', 'true', 'false', d)}; then
set_cfg_value src/client.conf allow-autospawn-for-root yes
fi
}
all that make sense?
rday
next reply other threads:[~2020-04-06 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 16:05 rpjday [this message]
2020-04-06 16:38 ` [OE-core] couple questions on PACKAGECONFIG (for improving docs) Quentin Schulz
2020-04-06 17:58 ` rpjday
2020-04-06 18:00 ` Richard Purdie
2020-04-06 18:01 ` rpjday
2020-04-06 18:21 ` Denys Dmytriyenko
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.21.2004061153450.16686@localhost.localdomain \
--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