diff options
Diffstat (limited to 'documentation/sdk-manual/appendix-obtain.rst')
-rw-r--r-- | documentation/sdk-manual/appendix-obtain.rst | 21 |
1 files changed, 9 insertions, 12 deletions
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 |