From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: question about EXPORT_FUNCTIONS from bitbake user manual
Date: Tue, 16 Jan 2024 07:11:39 -0500 (EST) [thread overview]
Message-ID: <c2e177fb-6447-98f-fd51-8017ea87294a@crashcourse.ca> (raw)
hoping that bitbake doc questions have been subsumed under the YP
docs mailing list ...
i'm reading the section, "Flexible Inheritance for Class Functions",
here:
https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html?highlight=inheritance#flexible-inheritance-for-class-functions
and i understand the point of examples like autotools.bbclass defining
task functions like "autotools_do_install" so recipes that "inherit
autotools" can define their own "do_install" function that, somewhere
internally, calls "autotools_do_install".
but what if the recipe that inherits autotools does *not* define its
own do_install() function? would it still pick up the
autotools_do_install? what if that recipe tried to:
do_install:append = ...
would that even make sense? which install function would it be
appending to?
in short, while that section explains how to invoke the "base" task
function, it is not clear what happens if you don't invoke it that
way, and just try to take advantage of the "default" do_install.
rday
next reply other threads:[~2024-01-16 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:11 Robert P. J. Day [this message]
2024-01-16 12:39 ` [docs] question about EXPORT_FUNCTIONS from bitbake user manual Richard Purdie
2024-01-16 12:50 ` Robert P. J. Day
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=c2e177fb-6447-98f-fd51-8017ea87294a@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=docs@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).