CaROS/poky
3
1
Fork 0
mirror of https://git.yoctoproject.org/git/poky synced 2026-01-01 13:58:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove OE_INIT_FILE variable

Browse Source 
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/adt-manual/adt-prepare.rst
View File

@ -107,7 +107,7 @@ the tarball using either of these methods:
configuration information.
$ cd ~ $ git clone git://git.yoctoproject.org/poky $ cd poky $ git
checkout -b DISTRO_NAME origin/DISTRO_NAME $ source OE_INIT_FILE $
checkout -b DISTRO_NAME origin/DISTRO_NAME $ source oe-init-build-env $
bitbake adt-installer
Configuring and Running the ADT Installer Script

2
documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
View File

@ -177,7 +177,7 @@ an entire Linux distribution, including the toolchain, from source.
.. code-block:: shell
$ cd ~/poky
$ source &OE_INIT_FILE;
$ source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf

2
documentation/bsp-guide/bsp.rst
View File

@ -233,7 +233,7 @@ section.
setup script to define the OpenEmbedded build environment on your
build host. ::
$ source &OE_INIT_FILE;
$ source oe-init-build-env
Among other things, the script creates the :term:`Build Directory`, which is
``build`` in this case and is located in the :term:`Source Directory`. After

1
documentation/poky.yaml
View File

@ -58,7 +58,6 @@ YOCTO_DOCS_BRIEF_URL : "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/brief-yoctoprojectq
YOCTO_ADTPATH_DIR : "/opt/poky/&DISTRO;"
YOCTO_POKY_TARBALL : "&YOCTO_POKY;.tar.bz2"
OE_INIT_PATH : "&YOCTO_POKY;/oe-init-build-env"
OE_INIT_FILE : "oe-init-build-env"
UBUNTU_HOST_PACKAGES_ESSENTIAL : "gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \

5
documentation/ref-manual/ref-structure.rst
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