From 7db69417c182d3a59699671ee4d059f8d4faf356 Mon Sep 17 00:00:00 2001 From: Quentin Schulz Date: Mon, 5 Oct 2020 20:37:24 +0200 Subject: 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 (From yocto-docs rev: 6fd4421283005b0ecc980e9ef25770d383b93937) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-structure.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/ref-structure.rst b/documentation/ref-manual/ref-structure.rst index ff5d863736..db1ea97979 100644 --- a/documentation/ref-manual/ref-structure.rst +++ b/documentation/ref-manual/ref-structure.rst @@ -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 -- cgit v1.2.3-54-g00ecf