docs: remove OE_INIT_FILE variable

There's probably no need for such a variable (the name of the script is
unlikely to change any time soon) and not all instances of
oe-init-build-env were actually using this variable.

For consistency sake, let's just remove the OE_INIT_FILE variable.

Suggested-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
(From yocto-docs rev: 6fd4421283005b0ecc980e9ef25770d383b93937)

Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2020-10-05 20:37:24 +02:00
committed by Richard Purdie
parent 8dd785f120
commit 7db69417c1
5 changed files with 5 additions and 7 deletions

View File

@@ -188,7 +188,7 @@ your choice. For example, the following command creates a Build
Directory named ``mybuilds/`` that is outside of the :term:`Source Directory`:
::
$ source OE_INIT_FILE ~/mybuilds
$ source oe-init-build-env ~/mybuilds
The OpenEmbedded build system uses the template configuration files, which
are found by default in the ``meta-poky/conf/`` directory in the Source
@@ -200,8 +200,7 @@ information.
.. note::
The OpenEmbedded build system does not support file or directory
names that contain spaces. If you attempt to run the
OE_INIT_FILE
names that contain spaces. If you attempt to run the ``oe-init-build-env``
script from a Source Directory that contains spaces in either the
filenames or directory names, the script returns an error indicating
no such file or directory. Be sure to use a Source Directory free of