Yocto Project Documentation
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <pkj@axis.com>
To: <docs@lists.yoctoproject.org>
Subject: [PATCH] ref-manual: Document the EXTERNALSRC_EXTENSIONS variable
Date: Tue, 19 Oct 2021 19:04:34 +0200	[thread overview]
Message-ID: <20211019170434.18700-1-pkj@axis.com> (raw)

EXTERNALSRC_EXTENSIONS is used to specify additional classes to inherit
when externalsrc is inherited.

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---

This of course assumes that the corresponding change to OE-Core is
accepted.

 documentation/ref-manual/variables.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 85f65cae35..8e7321fa20 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -2175,6 +2175,12 @@ system and gives an overview of their function and contents.
       ":ref:`dev-manual/common-tasks:building software from an external source`"
       section in the Yocto Project Development Tasks Manual.
 
+   :term:`EXTERNALSRC_EXTENSIONS`
+      When inheriting the :ref:`externalsrc <ref-classes-externalsrc>`
+      class, this variable contains a list of additional classes that will
+      also be inherited. This allows for extending the externalsrc
+      functionality when it is active.
+
    :term:`EXTRA_AUTORECONF`
       For recipes inheriting the :ref:`autotools <ref-classes-autotools>`
       class, you can use :term:`EXTRA_AUTORECONF` to specify extra options to


             reply	other threads:[~2021-10-19 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 17:04 Peter Kjellerstedt [this message]
2021-10-20 15:45 ` [docs] [PATCH] ref-manual: Document the EXTERNALSRC_EXTENSIONS variable Michael Opdenacker
     [not found] ` <16AFC7A64FAFF929.12113@lists.yoctoproject.org>
2021-11-05 16:20   ` Michael Opdenacker
2021-11-05 17:05     ` Peter Kjellerstedt

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=20211019170434.18700-1-pkj@axis.com \
    --to=pkj@axis.com \
    --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