All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH v2 2/6] ref-manual/structure.rst: document the site.conf file
Date: Mon, 03 Nov 2025 17:33:06 +0100	[thread overview]
Message-ID: <20251103-bitbake-setup-v2-2-89fbb14cfbbd@bootlin.com> (raw)
In-Reply-To: <20251103-bitbake-setup-v2-0-89fbb14cfbbd@bootlin.com>

This was not documented and its usage is going to increase massively
once users start using bitbake-setup. Add a description for this file as
well as an example on how bitbake-setup shares it for multiple builds,
to insist on the "site-wide" usage of this file.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Note: a link to bitbake-setup documentation comes in the next patch.
---
 documentation/ref-manual/structure.rst | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/documentation/ref-manual/structure.rst b/documentation/ref-manual/structure.rst
index a2f2fd450..f0205f0e5 100644
--- a/documentation/ref-manual/structure.rst
+++ b/documentation/ref-manual/structure.rst
@@ -343,6 +343,35 @@ Once the build process gets the sample file, it uses ``sed`` to substitute final
    version of the ``bblayers.conf.sample`` file in the ``meta-poky/conf/templates/default``
    directory.
 
+.. _structure-build-conf-site.conf:
+
+``build/conf/site.conf``
+========================
+
+This configuration file contains the site specific configurations for your build
+environment.
+
+You could for example edit this file to limit the number of threads used by
+:term:`BitBake` (:term:`BB_NUMBER_THREADS`) or set the location from which you
+want to access downloaded files (:term:`DL_DIR`).
+
+This file can be shared for multiple build directories. For example,
+``bitbake-setup`` makes the :ref:`structure-build-conf-site.conf` file a
+symbolic link to a common ``site.conf`` file::
+
+   ├── poky-master-poky-distro_poky-machine_qemux86-64/
+   │   └── build/
+   │       └── conf/
+   │           └── site.conf -> ../../../site.conf
+   ├── poky-master-poky-with-sstate-distro_poky-machine_qemux86-64/
+   │   └── build/
+   │       └── conf/
+   │           └── site.conf -> ../../../site.conf
+   └── site.conf
+
+This way, site-specific settings can be shared for multiple build
+configurations.
+
 .. _structure-build-conf-bblock.conf:
 
 ``build/conf/bblock.conf``

-- 
2.51.0



  parent reply	other threads:[~2025-11-03 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 16:33 [PATCH v2 0/6] Start switching the documentation to bitbake-setup Antonin Godard
2025-11-03 16:33 ` [PATCH v2 1/6] ref-manual/structure.rst: update the description of local.conf and bblayers.conf Antonin Godard
2025-11-03 16:33 ` Antonin Godard [this message]
2025-11-03 16:33 ` [PATCH v2 3/6] brief-yoctoprojectqs: delete unused figures Antonin Godard
2025-11-03 16:33 ` [PATCH v2 4/6] brief-yoctoprojectqs: switch to bitbake-setup Antonin Godard
2025-11-04 13:09   ` [docs] " Alexander Kanavin
2025-11-05  8:24     ` Antonin Godard
2025-11-03 16:33 ` [PATCH v2 5/6] dev-manual: add a document to setup poky manually Antonin Godard
2025-11-03 16:33 ` [PATCH v2 6/6] ref-manual/terms.rst: update Poky description Antonin Godard

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=20251103-bitbake-setup-v2-2-89fbb14cfbbd@bootlin.com \
    --to=antonin.godard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.