From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 2/2] manuals: document SPLASH_IMAGES variable
Date: Fri, 26 May 2023 13:43:22 +0200 [thread overview]
Message-ID: <20230526114322.1698988-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230526114322.1698988-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
.../dev-manual/custom-distribution.rst | 9 +++---
documentation/ref-manual/variables.rst | 32 +++++++++++++++++++
2 files changed, 37 insertions(+), 4 deletions(-)
diff --git a/documentation/dev-manual/custom-distribution.rst b/documentation/dev-manual/custom-distribution.rst
index e5b1ad777a..47faed0d04 100644
--- a/documentation/dev-manual/custom-distribution.rst
+++ b/documentation/dev-manual/custom-distribution.rst
@@ -98,11 +98,12 @@ layer. The following steps provide some more detail:
- Add any image recipes that are specific to your distribution.
- - Add a ``psplash`` append file for a branded splash screen. For
- information on append files, see the
- ":ref:`dev-manual/layers:appending other layers metadata with your layer`"
- section.
+ - Add a ``psplash`` append file for a branded splash screen, using
+ the :term:`SPLASH_IMAGES` variable.
- Add any other append files to make custom changes that are
specific to individual recipes.
+ For information on append files, see the
+ ":ref:`dev-manual/layers:appending other layers metadata with your layer`"
+ section.
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 6680322f4c..6a7888ab47 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7826,6 +7826,38 @@ system and gives an overview of their function and contents.
for such applications to use. This variable is set by default to
``psplash``.
+ :term:`SPLASH_IMAGES`
+ This variable, used by the ``psplash`` recipe, allows to customize
+ the default splashscreen image.
+
+ Specified images in PNG format are converted to ``.h`` files by the recipe,
+ and are included in the ``psplash`` binary, so you won't find them in
+ the root filesystem.
+
+ To make such a change, it is recommended to customize the
+ ``psplash`` recipe in a custom layer. Here is an example structure for
+ an ``ACME`` board::
+
+ meta-acme/recipes-core/psplash
+ ├── files
+ │ └── logo-acme.png
+ └── psplash_%.bbappend
+
+ And here are the contents of the ``psplash_%.bbappend`` file in
+ this example::
+
+ SPLASH_IMAGES = "file://logo-acme.png;outsuffix=default"
+ FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
+
+ You could even add specific configuration options for ``psplash``,
+ for example::
+
+ EXTRA_OECONF += "--disable-startup-msg --enable-img-fullscreen"
+
+ For information on append files, see the
+ ":ref:`dev-manual/layers:appending other layers metadata with your layer`"
+ section.
+
:term:`SRCREV_FORMAT`
See :term:`bitbake:SRCREV_FORMAT` in the BitBake manual.
--
2.34.1
prev parent reply other threads:[~2023-05-26 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 11:43 [PATCH 1/2] ref-manual: document SPLASH variable michael.opdenacker
2023-05-26 11:43 ` michael.opdenacker [this message]
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=20230526114322.1698988-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