diff options
| -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. Installing the Extensible SDK ============================= -Two ways to install the Extensible SDK --------------------------------------- - -Extensible SDK can be installed in two different ways, and both have -their own pros and cons: - -#. *Setting up the Extensible SDK environment directly in a Yocto build*. This - avoids having to produce, test, distribute and maintain separate SDK - installer archives, which can get very large. There is only one environment - for the regular Yocto build and the SDK and less code paths where things can - go not according to plan. It's easier to update the SDK: it simply means - updating the Yocto layers with git fetch or layer management tooling. The - SDK extensibility is better than in the second option: just run ``bitbake`` - again to add more things to the sysroot, or add layers if even more things - are required. - -#. *Setting up the Extensible SDK from a standalone installer*. This has the - benefit of having a single, self-contained archive that includes all the - needed binary artifacts. So nothing needs to be rebuilt, and there is no - need to provide a well-functioning binary artefact cache over the network - for developers with underpowered laptops. - -Setting up the Extensible SDK environment directly in a Yocto build -------------------------------------------------------------------- - -#. Set up all the needed layers and a Yocto :term:`Build Directory`, e.g. a regular Yocto - build where ``bitbake`` can be executed. - -#. Run:: - - $ bitbake meta-ide-support - $ bitbake -c populate_sysroot gtk+3 - # or any other target or native item that the application developer would need - $ bitbake build-sysroots - -Setting up the Extensible SDK from a standalone installer ---------------------------------------------------------- - The first thing you need to do is install the SDK on your :term:`Build Host` by running the ``*.sh`` installation script. @@ -172,12 +134,7 @@ Running the Extensible SDK Environment Setup Script =================================================== Once you have the SDK installed, you must run the SDK environment setup -script before you can actually use the SDK. - -When using a SDK directly in a Yocto build, you will find the script in -``tmp/deploy/images/qemux86-64/`` in your :term:`Build Directory`. - -When using a standalone SDK installer, this setup script resides in +script before you can actually use the SDK. This setup script resides in the directory you chose when you installed the SDK, which is either the default ``poky_sdk`` directory or the directory you chose during installation. @@ -195,11 +152,6 @@ script is for an IA-based target machine using i586 tuning:: SDK environment now set up; additionally you may now run devtool to perform development tasks. Run devtool --help for further details. -When using the environment script directly in a Yocto build, it can -be run similarly:: - - $ source tmp/deploy/images/qemux86-64/environment-setup-core2-64-poky-linux - Running the setup script defines many environment variables needed in order to use the SDK (e.g. ``PATH``, :term:`CC`, :term:`LD`, and so forth). If you want to see all the environment variables the script exports, examine the @@ -1219,19 +1171,6 @@ You can use the following command to find out:: Once you know the recipe (i.e. ``mesa`` in this example), you can install it. -When using the extensible SDK directly in a Yocto build -------------------------------------------------------- - -In this scenario, the Yocto build tooling, e.g. ``bitbake`` -is directly accessible to build additional items, and it -can simply be executed directly:: - - $ bitbake mesa - $ bitbake build-sysroots - -When using a standalone installer for the Extensible SDK --------------------------------------------------------- - :: $ devtool sdk-install mesa |