From patchwork Mon Jan 12 16:36:11 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Quentin Schulz X-Patchwork-Id: 78521 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A9B2CF45A4 for ; Mon, 12 Jan 2026 16:36:44 +0000 (UTC) Received: from smtp-bc0c.mail.infomaniak.ch (smtp-bc0c.mail.infomaniak.ch [45.157.188.12]) by mx.groups.io with SMTP id smtpd.msgproc02-g2.36923.1768235799324145829 for ; Mon, 12 Jan 2026 08:36:39 -0800 Authentication-Results: mx.groups.io; dkim=none (message not signed); spf=pass (domain: 0leil.net, ip: 45.157.188.12, mailfrom: foss+yocto@0leil.net) Received: from smtp-3-0000.mail.infomaniak.ch (unknown [IPv6:2001:1600:4:17::246b]) by smtp-3-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4dqdLY47xZzmVy; Mon, 12 Jan 2026 17:36:37 +0100 (CET) Received: from unknown by smtp-3-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4dqdLY1BCNzddD; Mon, 12 Jan 2026 17:36:37 +0100 (CET) From: Quentin Schulz Date: Mon, 12 Jan 2026 17:36:11 +0100 Subject: [PATCH 7/8] doc: bitbake-user-manual-metadata: expand on search paths for include directive MIME-Version: 1.0 Message-Id: <20260112-doc-directives-v1-7-b23923cfce89@cherry.de> References: <20260112-doc-directives-v1-0-b23923cfce89@cherry.de> In-Reply-To: <20260112-doc-directives-v1-0-b23923cfce89@cherry.de> To: bitbake-devel@lists.openembedded.org Cc: docs@lists.yoctoproject.org, Quentin Schulz X-Mailer: b4 0.14.3 X-Infomaniak-Routing: alpha List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Mon, 12 Jan 2026 16:36:44 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/bitbake-devel/message/18741 From: Quentin Schulz While it is made somewhat explicit in the require and include directive sections, I believe we should provide an example as to which relative directory the include/require directives apply to when in a bbappend. Let's provide some example to make this even clearer as it wasn't what I thought would happen. Signed-off-by: Quentin Schulz --- doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst index 719689150..cbad4df99 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst @@ -1112,6 +1112,18 @@ In this case, the following paths would be searched:: This time, the second item of this list would be matched. +Note that the first path is based on the location of the file with the +``require`` (or ``include``) directive. Imagine there's a +``/layers/meta-custom2/recipes-bbappend/example/example_0.1.bbappend`` with:: + + require myappend.inc + +In this case, the following paths would be searched:: + + /layers/meta-custom2/recipes-bbappend/example/myappend.inc + /layers/meta-custom1/myappend.inc + /layers/meta-custom2/myappend.inc + .. note:: In the above examples, the exact same search order applies for the