diff options
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/sdk-manual/extensible.rst | 63 |
1 files changed, 1 insertions, 62 deletions
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index 355c6cb0e4..7edb3eb4b4 100644 --- a/documentation/sdk-manual/extensible.rst +++ b/documentation/sdk-manual/extensible.rst | |||
| @@ -41,44 +41,6 @@ functionality. | |||
| 41 | Installing the Extensible SDK | 41 | Installing the Extensible SDK |
| 42 | ============================= | 42 | ============================= |
| 43 | 43 | ||
| 44 | Two ways to install the Extensible SDK | ||
| 45 | -------------------------------------- | ||
| 46 | |||
| 47 | Extensible SDK can be installed in two different ways, and both have | ||
| 48 | their own pros and cons: | ||
| 49 | |||
| 50 | #. *Setting up the Extensible SDK environment directly in a Yocto build*. This | ||
| 51 | avoids having to produce, test, distribute and maintain separate SDK | ||
| 52 | installer archives, which can get very large. There is only one environment | ||
| 53 | for the regular Yocto build and the SDK and less code paths where things can | ||
| 54 | go not according to plan. It's easier to update the SDK: it simply means | ||
| 55 | updating the Yocto layers with git fetch or layer management tooling. The | ||
| 56 | SDK extensibility is better than in the second option: just run ``bitbake`` | ||
| 57 | again to add more things to the sysroot, or add layers if even more things | ||
| 58 | are required. | ||
| 59 | |||
| 60 | #. *Setting up the Extensible SDK from a standalone installer*. This has the | ||
| 61 | benefit of having a single, self-contained archive that includes all the | ||
| 62 | needed binary artifacts. So nothing needs to be rebuilt, and there is no | ||
| 63 | need to provide a well-functioning binary artefact cache over the network | ||
| 64 | for developers with underpowered laptops. | ||
| 65 | |||
| 66 | Setting up the Extensible SDK environment directly in a Yocto build | ||
| 67 | ------------------------------------------------------------------- | ||
| 68 | |||
| 69 | #. Set up all the needed layers and a Yocto :term:`Build Directory`, e.g. a regular Yocto | ||
| 70 | build where ``bitbake`` can be executed. | ||
| 71 | |||
| 72 | #. Run:: | ||
| 73 | |||
| 74 | $ bitbake meta-ide-support | ||
| 75 | $ bitbake -c populate_sysroot gtk+3 | ||
| 76 | # or any other target or native item that the application developer would need | ||
| 77 | $ bitbake build-sysroots | ||
| 78 | |||
| 79 | Setting up the Extensible SDK from a standalone installer | ||
| 80 | --------------------------------------------------------- | ||
| 81 | |||
| 82 | The first thing you need to do is install the SDK on your :term:`Build | 44 | The first thing you need to do is install the SDK on your :term:`Build |
| 83 | Host` by running the ``*.sh`` installation script. | 45 | Host` by running the ``*.sh`` installation script. |
| 84 | 46 | ||
| @@ -172,12 +134,7 @@ Running the Extensible SDK Environment Setup Script | |||
| 172 | =================================================== | 134 | =================================================== |
| 173 | 135 | ||
| 174 | Once you have the SDK installed, you must run the SDK environment setup | 136 | Once you have the SDK installed, you must run the SDK environment setup |
| 175 | script before you can actually use the SDK. | 137 | script before you can actually use the SDK. This setup script resides in |
| 176 | |||
| 177 | When using a SDK directly in a Yocto build, you will find the script in | ||
| 178 | ``tmp/deploy/images/qemux86-64/`` in your :term:`Build Directory`. | ||
| 179 | |||
| 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 | 138 | the directory you chose when you installed the SDK, which is either the |
| 182 | default ``poky_sdk`` directory or the directory you chose during | 139 | default ``poky_sdk`` directory or the directory you chose during |
| 183 | installation. | 140 | installation. |
| @@ -195,11 +152,6 @@ script is for an IA-based target machine using i586 tuning:: | |||
| 195 | SDK environment now set up; additionally you may now run devtool to perform development tasks. | 152 | SDK environment now set up; additionally you may now run devtool to perform development tasks. |
| 196 | Run devtool --help for further details. | 153 | Run devtool --help for further details. |
| 197 | 154 | ||
| 198 | When using the environment script directly in a Yocto build, it can | ||
| 199 | be run similarly:: | ||
| 200 | |||
| 201 | $ source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux | ||
| 202 | |||
| 203 | Running the setup script defines many environment variables needed in order to | 155 | Running the setup script defines many environment variables needed in order to |
| 204 | use the SDK (e.g. ``PATH``, :term:`CC`, :term:`LD`, and so forth). If you want | 156 | use the SDK (e.g. ``PATH``, :term:`CC`, :term:`LD`, and so forth). If you want |
| 205 | to see all the environment variables the script exports, examine the | 157 | to see all the environment variables the script exports, examine the |
| @@ -1219,19 +1171,6 @@ You can use the following command to find out:: | |||
| 1219 | Once you know the recipe | 1171 | Once you know the recipe |
| 1220 | (i.e. ``mesa`` in this example), you can install it. | 1172 | (i.e. ``mesa`` in this example), you can install it. |
| 1221 | 1173 | ||
| 1222 | When using the extensible SDK directly in a Yocto build | ||
| 1223 | ------------------------------------------------------- | ||
| 1224 | |||
| 1225 | In this scenario, the Yocto build tooling, e.g. ``bitbake`` | ||
| 1226 | is directly accessible to build additional items, and it | ||
| 1227 | can simply be executed directly:: | ||
| 1228 | |||
| 1229 | $ bitbake mesa | ||
| 1230 | $ bitbake build-sysroots | ||
| 1231 | |||
| 1232 | When using a standalone installer for the Extensible SDK | ||
| 1233 | -------------------------------------------------------- | ||
| 1234 | |||
| 1235 | :: | 1174 | :: |
| 1236 | 1175 | ||
| 1237 | $ devtool sdk-install mesa | 1176 | $ devtool sdk-install mesa |
