From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 2/2] dev-manual: new-recipe.rst: add references to subsections in Examples section
Date: Thu, 23 Feb 2023 16:37:29 +0100 [thread overview]
Message-ID: <20230223153729.2492175-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230223153729.2492175-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Making it possible to jump right away to the desired example
Rename a section title to make it more suitable for a link title.
Using short references (`Section Name`_) instead of
:ref:`dev-manual/new-recipe:Section Name`) as we are in the same
document.
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/dev-manual/new-recipe.rst | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/documentation/dev-manual/new-recipe.rst b/documentation/dev-manual/new-recipe.rst
index 9f00ac198f..d8cedbf7a4 100644
--- a/documentation/dev-manual/new-recipe.rst
+++ b/documentation/dev-manual/new-recipe.rst
@@ -361,7 +361,7 @@ and searches specific directories in a certain order:
``files``. The directories are assumed to be subdirectories of the
directory in which the recipe or append file resides. For another
example that specifies these types of files, see the
-":ref:`dev-manual/new-recipe:building a single .c file package (hello world!)`" section.
+"`building a single .c file package`_" section.
The previous example also specifies a patch file. Patch files are files
whose names usually end in ``.patch`` or ``.diff`` but can end with
@@ -1167,20 +1167,20 @@ Examples
To help summarize how to write a recipe, this section provides some
recipe examples given various scenarios:
-- Building packages from a single local file
+- `Building a single .c file package`_
-- Building a Makefile-based package
+- `Building a Makefile-based package`_
-- Building an Autotooled package
+- `Building an Autotooled package`_
-- Building a Meson package
+- `Building a Meson package`_
-- Splitting an application into multiple packages
+- `Splitting an application into multiple packages`_
-- Adding binaries to an image
+- `Packaging externally produced binaries`_
-Building a Single .c File Package (Hello World!)
-------------------------------------------------
+Building a Single .c File Package
+---------------------------------
Building an application from a single file that is stored locally (e.g. under
``files``) requires a recipe that has the file listed in the :term:`SRC_URI`
--
2.37.2
next prev parent reply other threads:[~2023-02-23 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 15:37 [PATCH 1/2] dev-manual: new-recipe.rst: add Meson example recipe michael.opdenacker
2023-02-23 15:37 ` michael.opdenacker [this message]
2023-02-24 10:17 ` [docs] " Quentin Schulz
2023-02-24 15:40 ` Michael Opdenacker
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=20230223153729.2492175-2-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.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