diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-10-27 15:09:08 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-10-28 15:48:03 +0100 |
commit | b44fbe5b1b425b8a8c23e4f0ba80583944ab303a (patch) | |
tree | 5e1787b385f95ffaf7fa2cf5507ff2a91ef39d07 /documentation/sdk-manual | |
parent | 50458d923826ae96deaf799fa7ee1e0584cb57ff (diff) | |
download | poky-b44fbe5b1b425b8a8c23e4f0ba80583944ab303a.tar.gz |
manuals: use references to the "Build Directory" term
Replace instances of "Build Directory" and "build directory"
(when applicable) by :term:`Build Directory` as already
done in most places.
Doing this, fix the indentation of the paragraphs with
this term.
(From yocto-docs rev: dce50679242d39f133e0cde5c8483b5e69f3eb54)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual')
-rw-r--r-- | documentation/sdk-manual/appendix-customizing.rst | 5 | ||||
-rw-r--r-- | documentation/sdk-manual/appendix-obtain.rst | 21 | ||||
-rw-r--r-- | documentation/sdk-manual/extensible.rst | 4 |
3 files changed, 13 insertions, 17 deletions
diff --git a/documentation/sdk-manual/appendix-customizing.rst b/documentation/sdk-manual/appendix-customizing.rst index 23a437eb9d..d6bca44947 100644 --- a/documentation/sdk-manual/appendix-customizing.rst +++ b/documentation/sdk-manual/appendix-customizing.rst | |||
@@ -286,9 +286,8 @@ source, you need to do a number of things: | |||
286 | ESDK_LOCALCONF_ALLOW = "SSTATE_MIRRORS" | 286 | ESDK_LOCALCONF_ALLOW = "SSTATE_MIRRORS" |
287 | 287 | ||
288 | - Alternatively, if you just want to set the :term:`SSTATE_MIRRORS` | 288 | - Alternatively, if you just want to set the :term:`SSTATE_MIRRORS` |
289 | variable's value for the SDK alone, create a | 289 | variable's value for the SDK alone, create a ``conf/sdk-extra.conf`` |
290 | ``conf/sdk-extra.conf`` file either in your | 290 | file either in your :term:`Build Directory` or within any |
291 | :term:`Build Directory` or within any | ||
292 | layer and put your :term:`SSTATE_MIRRORS` setting within that file. | 291 | layer and put your :term:`SSTATE_MIRRORS` setting within that file. |
293 | 292 | ||
294 | .. note:: | 293 | .. note:: |
diff --git a/documentation/sdk-manual/appendix-obtain.rst b/documentation/sdk-manual/appendix-obtain.rst index 7d62293cd6..b90247d2e0 100644 --- a/documentation/sdk-manual/appendix-obtain.rst +++ b/documentation/sdk-manual/appendix-obtain.rst | |||
@@ -116,24 +116,21 @@ build the SDK installer. Follow these steps: | |||
116 | 116 | ||
117 | $ source oe-init-build-env | 117 | $ source oe-init-build-env |
118 | 118 | ||
119 | Among other things, the script | 119 | Among other things, the script creates the :term:`Build Directory`, which |
120 | creates the :term:`Build Directory`, | 120 | is ``build`` in this case and is located in the Source Directory. After |
121 | which is | 121 | the script runs, your current working directory is set to the ``build`` |
122 | ``build`` in this case and is located in the Source Directory. After | 122 | directory. |
123 | the script runs, your current working directory is set to the | ||
124 | ``build`` directory. | ||
125 | 123 | ||
126 | 4. *Make Sure You Are Building an Installer for the Correct Machine:* | 124 | 4. *Make Sure You Are Building an Installer for the Correct Machine:* |
127 | Check to be sure that your | 125 | Check to be sure that your :term:`MACHINE` variable in the ``local.conf`` |
128 | :term:`MACHINE` variable in the | 126 | file in your :term:`Build Directory` matches the architecture |
129 | ``local.conf`` file in your Build Directory matches the architecture | ||
130 | for which you are building. | 127 | for which you are building. |
131 | 128 | ||
132 | 5. *Make Sure Your SDK Machine is Correctly Set:* If you are building a | 129 | 5. *Make Sure Your SDK Machine is Correctly Set:* If you are building a |
133 | toolchain designed to run on an architecture that differs from your | 130 | toolchain designed to run on an architecture that differs from your |
134 | current development host machine (i.e. the build host), be sure that | 131 | current development host machine (i.e. the build host), be sure that |
135 | the :term:`SDKMACHINE` variable in the ``local.conf`` file in your | 132 | the :term:`SDKMACHINE` variable in the ``local.conf`` file in your |
136 | Build Directory is correctly set. | 133 | :term:`Build Directory` is correctly set. |
137 | 134 | ||
138 | .. note:: | 135 | .. note:: |
139 | 136 | ||
@@ -163,7 +160,7 @@ build the SDK installer. Follow these steps: | |||
163 | that matches your target root filesystem. | 160 | that matches your target root filesystem. |
164 | 161 | ||
165 | When the ``bitbake`` command completes, the SDK installer will be in | 162 | When the ``bitbake`` command completes, the SDK installer will be in |
166 | ``tmp/deploy/sdk`` in the Build Directory. | 163 | ``tmp/deploy/sdk`` in the :term:`Build Directory`. |
167 | 164 | ||
168 | .. note:: | 165 | .. note:: |
169 | 166 | ||
@@ -180,7 +177,7 @@ build the SDK installer. Follow these steps: | |||
180 | libc-staticdev" | 177 | libc-staticdev" |
181 | 178 | ||
182 | 7. *Run the Installer:* You can now run the SDK installer from | 179 | 7. *Run the Installer:* You can now run the SDK installer from |
183 | ``tmp/deploy/sdk`` in the Build Directory. Following is an example:: | 180 | ``tmp/deploy/sdk`` in the :term:`Build Directory`. Following is an example:: |
184 | 181 | ||
185 | $ cd poky/build/tmp/deploy/sdk | 182 | $ cd poky/build/tmp/deploy/sdk |
186 | $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh | 183 | $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh |
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index 3e3fa6c05a..ed38ac3f3f 100644 --- a/documentation/sdk-manual/extensible.rst +++ b/documentation/sdk-manual/extensible.rst | |||
@@ -64,7 +64,7 @@ binary artefact cache over the network for developers with underpowered laptops. | |||
64 | Setting up the Extensible SDK environment directly in a Yocto build | 64 | Setting up the Extensible SDK environment directly in a Yocto build |
65 | ------------------------------------------------------------------- | 65 | ------------------------------------------------------------------- |
66 | 66 | ||
67 | 1. Set up all the needed layers and a Yocto build directory, e.g. a regular Yocto | 67 | 1. Set up all the needed layers and a Yocto :term:`Build Directory`, e.g. a regular Yocto |
68 | build where ``bitbake`` can be executed. | 68 | build where ``bitbake`` can be executed. |
69 | 69 | ||
70 | 2. Run: | 70 | 2. Run: |
@@ -175,7 +175,7 @@ Once you have the SDK installed, you must run the SDK environment setup | |||
175 | script before you can actually use the SDK. | 175 | script before you can actually use the SDK. |
176 | 176 | ||
177 | When using a SDK directly in a Yocto build, you will find the script in | 177 | When using a SDK directly in a Yocto build, you will find the script in |
178 | ``tmp/deploy/images/qemux86-64/`` in your build directory. | 178 | ``tmp/deploy/images/qemux86-64/`` in your :term:`Build Directory`. |
179 | 179 | ||
180 | When using a standalone SDK installer, this setup script resides in | 180 | When using a standalone SDK installer, this setup script resides in |
181 | the directory you chose when you installed the SDK, which is either the | 181 | the directory you chose when you installed the SDK, which is either the |