Yocto Project Documentation
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [RFC 2/3] ref-manual: move TMPDIR to BitBake's documentation
Date: Fri,  5 Nov 2021 16:11:58 +0100	[thread overview]
Message-ID: <20211105151159.28541-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20211105151159.28541-1-michael.opdenacker@bootlin.com>

As it is not specific to OE / Yocto Project

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 documentation/ref-manual/variables.rst | 21 ---------------------
 1 file changed, 21 deletions(-)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 441a10929e..44fccd5322 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -8022,27 +8022,6 @@ system and gives an overview of their function and contents.
       and second (HMS) format (e.g. "140159" for one minute and fifty-nine
       seconds past 1400 hours).
 
-   :term:`TMPDIR`
-      This variable is the base directory the OpenEmbedded build system
-      uses for all build output and intermediate files (other than the
-      shared state cache). By default, the :term:`TMPDIR` variable points to
-      ``tmp`` within the :term:`Build Directory`.
-
-      If you want to establish this directory in a location other than the
-      default, you can uncomment and edit the following statement in the
-      ``conf/local.conf`` file in the :term:`Source Directory`::
-
-         #TMPDIR = "${TOPDIR}/tmp"
-
-      An example use for this scenario is to set :term:`TMPDIR` to a local disk,
-      which does not use NFS, while having the Build Directory use NFS.
-
-      The filesystem used by :term:`TMPDIR` must have standard filesystem
-      semantics (i.e. mixed-case files are unique, POSIX file locking, and
-      persistent inodes). Due to various issues with NFS and bugs in some
-      implementations, NFS does not meet this minimum requirement.
-      Consequently, :term:`TMPDIR` cannot be on NFS.
-
    :term:`TOOLCHAIN_HOST_TASK`
       This variable lists packages the OpenEmbedded build system uses when
       building an SDK, which contains a cross-development environment. The
-- 
2.25.1



  parent reply	other threads:[~2021-11-05 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 15:11 [PATCH 0/3] Simplify variable reference descriptions Michael Opdenacker
2021-11-05 15:11 ` [RFC 1/3] ref-manual: simplify SRC_URI reference Michael Opdenacker
2021-11-05 15:11 ` Michael Opdenacker [this message]
2021-11-05 15:11 ` [RFC 3/3] ref-manual: move TOPDIR to BitBake's manual 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=20211105151159.28541-3-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