From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [RFC PATCH] doc: Add section on creating new layers
Date: Tue, 3 Sep 2019 13:50:25 +0200 [thread overview]
Message-ID: <20190903115025.5007-1-ada@thorsis.com> (raw)
After discussing these topics in IRC, it seemed reasonable to add some
explanation on how to create a new layer from scratch.
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
doc/dev_manual.rst | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
index d79ebdba7..746f3d695 100644
--- a/doc/dev_manual.rst
+++ b/doc/dev_manual.rst
@@ -1631,6 +1631,8 @@ convenient way to crate simple templates. It is also possible to create
more files. For examples, the builtin ``genimage`` template creates a extra
config file for the new package.
+.. _layers:
+
Layers in PTXdist
-----------------
@@ -1740,3 +1742,32 @@ layer.
The make macros that provide these features are currently used by the
barebox and kernel packages and templates.
+
+Creating a new Layer
+~~~~~~~~~~~~~~~~~~~~
+
+Adding new layers on top of an already existing BSP is easy:
+
+#. Create an empty folder, e.g. next to the existing BSP.
+#. The lower layer is just a folder named ``base`` (see layers_ above). You
+ may do one of the following (or something else you consider convenient):
+
+ - Create a symbolic link ``base`` to an outside laying BSP folder. For
+ an easy start, you can try this method with DistroKit_ for example:
+ ``$ ln -s ../DistroKit base``
+ - Use a Git submodule with a BSP in a folder ``base``.
+ - Copy over your whole existing BSP to a new subfolder ``base``.
+
+#. If needed select **ptxconfig** and/or **platformconfig** after copying
+ that file from the lower layer to your new layer:
+
+.. code-block:: text
+
+ $ mkdir -p configs/platform-v7a
+ $ cp base/configs/platform-v7a/platformconfig configs/platform-v7a/
+ $ ptxdist platform configs/platform-v7a/platformconfig
+
+#. Use ``ptxdist menu`` like usual.
+#. Put your new layer into Git and add configs and delta configs to it.
+
+.. _DistroKit: https://www.pengutronix.de/de/software/distrokit.html
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-09-03 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:50 Alexander Dahl [this message]
2019-09-03 12:00 ` Roland Hieber
2019-09-03 12:22 ` Alexander Dahl
2019-09-03 13:08 ` Michael Olbrich
2019-09-03 13:38 ` Roland Hieber
2019-09-03 14:12 ` Michael Olbrich
2019-09-04 10:30 ` Roland Hieber
2019-09-04 12:55 ` Roland Hieber
2019-09-03 13:48 ` Alexander Dahl
2019-09-03 14:22 ` Michael Olbrich
2019-09-03 18:49 ` Alexander Dahl
2019-09-04 5:37 ` Michael Olbrich
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=20190903115025.5007-1-ada@thorsis.com \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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