diff options
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-12-17 04:11:34 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-01-09 02:21:44 +0300 |
commit | 1a4b7ee28bf7413af6513fb45ad0d0736048f866 (patch) | |
tree | 79f6d8ea698cab8f2eaf4f54b793d2ca7a1451ce /poky/documentation/sdk-manual/sdk-appendix-customizing.xml | |
parent | 5b9ede0403237c7dace972affa65cf64a1aadd0e (diff) | |
download | openbmc-1a4b7ee28bf7413af6513fb45ad0d0736048f866.tar.xz |
reset upstream subtrees to yocto 2.6
Reset the following subtrees on thud HEAD:
poky: 87e3a9739d
meta-openembedded: 6094ae18c8
meta-security: 31dc4e7532
meta-raspberrypi: a48743dc36
meta-xilinx: c42016e2e6
Also re-apply backports that didn't make it into thud:
poky:
17726d0 systemd-systemctl-native: handle Install wildcards
meta-openembedded:
4321a5d libtinyxml2: update to 7.0.1
042f0a3 libcereal: Add native and nativesdk classes
e23284f libcereal: Allow empty package
030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG
179a1b9 gtest: update to 1.8.1
Squashed OpenBMC subtree compatibility updates:
meta-aspeed:
Brad Bishop (1):
aspeed: add yocto 2.6 compatibility
meta-ibm:
Brad Bishop (1):
ibm: prepare for yocto 2.6
meta-ingrasys:
Brad Bishop (1):
ingrasys: set layer compatibility to yocto 2.6
meta-openpower:
Brad Bishop (1):
openpower: set layer compatibility to yocto 2.6
meta-phosphor:
Brad Bishop (3):
phosphor: set layer compatibility to thud
phosphor: libgpg-error: drop patches
phosphor: react to fitimage artifact rename
Ed Tanous (4):
Dropbear: upgrade options for latest upgrade
yocto2.6: update openssl options
busybox: remove upstream watchdog patch
systemd: Rebase CONFIG_CGROUP_BPF patch
Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'poky/documentation/sdk-manual/sdk-appendix-customizing.xml')
-rw-r--r-- | poky/documentation/sdk-manual/sdk-appendix-customizing.xml | 76 |
1 files changed, 72 insertions, 4 deletions
diff --git a/poky/documentation/sdk-manual/sdk-appendix-customizing.xml b/poky/documentation/sdk-manual/sdk-appendix-customizing.xml index c3215e622..7454c90be 100644 --- a/poky/documentation/sdk-manual/sdk-appendix-customizing.xml +++ b/poky/documentation/sdk-manual/sdk-appendix-customizing.xml @@ -7,7 +7,7 @@ <title>Customizing the Extensible SDK</title> <para> - This appendix presents customizations you can apply to the extensible SDK. + This appendix describes customizations you can apply to the extensible SDK. </para> <section id='sdk-configuring-the-extensible-sdk'> @@ -186,7 +186,13 @@ You can change the displayed title for the SDK installer by setting the <ulink url='&YOCTO_DOCS_REF_URL;#var-SDK_TITLE'><filename>SDK_TITLE</filename></ulink> - variable. + variable and then rebuilding the the SDK installer. + For information on how to build an SDK installer, see the + "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>" + section. + </para> + + <para> By default, this title is derived from <ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO_NAME'><filename>DISTRO_NAME</filename></ulink> when it is set. @@ -198,11 +204,28 @@ <para> The - <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-populate-sdk-*'><filename>populate_sdk_ext</filename></ulink> + <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-populate-sdk-*'><filename>populate_sdk_base</filename></ulink> class defines the default value of the <filename>SDK_TITLE</filename> variable as follows: <literallayout class='monospaced'> - SDK_TITLE_task-populate-sdk-ext = "${@d.getVar('DISTRO_NAME') or d.getVar('DISTRO')} Extensible SDK" + SDK_TITLE ??= "${@d.getVar('DISTRO_NAME') or d.getVar('DISTRO')} SDK" + </literallayout> + </para> + + <para> + While several ways exist to change this variable, an efficient method + is to set the variable in your distribution's configuration file. + Doing so creates an SDK installer title that applies across your + distribution. + As an example, assume you have your own layer for your distribution + named "meta-mydistro" and you are using the same type of file + hierarchy as does the default "poky" distribution. + If so, you could update the <filename>SDK_TITLE</filename> variable + in the + <filename>~/meta-mydistro/conf/distro/mydistro.conf</filename> file + using the following form: + <literallayout class='monospaced'> + SDK_TITLE = "<replaceable>your_title</replaceable>" </literallayout> </para> </section> @@ -265,6 +288,51 @@ </para> </section> +<section id='sdk-changing-the-default-sdk-installation-directory'> + <title>Changing the Default SDK Installation Directory</title> + + <para> + When you build the installer for the Extensible SDK, the default + installation directory for the SDK is based on the + <ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO'><filename>DISTRO</filename></ulink> + and + <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKEXTPATH'><filename>SDKEXTPATH</filename></ulink> + variables from within the + <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-populate-sdk-*'><filename>populate_sdk_base</filename></ulink> + class as follows: + <literallayout class='monospaced'> + SDKEXTPATH ??= "~/${@d.getVar('DISTRO')}_sdk" + </literallayout> + You can change this default installation directory by specifically + setting the <filename>SDKEXTPATH</filename> variable. + </para> + + <para> + While a number of ways exist through which you can set this variable, + the method that makes the most sense is to set the variable in your + distribution's configuration file. + Doing so creates an SDK installer default directory that applies + across your distribution. + As an example, assume you have your own layer for your distribution + named "meta-mydistro" and you are using the same type of file + hierarchy as does the default "poky" distribution. + If so, you could update the <filename>SDKEXTPATH</filename> variable + in the + <filename>~/meta-mydistro/conf/distro/mydistro.conf</filename> file + using the following form: + <literallayout class='monospaced'> + SDKEXTPATH = "<replaceable>some_path_for_your_installed_sdk</replaceable>" + </literallayout> + </para> + + <para> + After building your installer, running it prompts the user for + acceptance of the + <replaceable>some_path_for_your_installed_sdk</replaceable> directory + as the default location to install the Extensible SDK. + </para> +</section> + <section id='sdk-providing-additional-installable-extensible-sdk-content'> <title>Providing Additional Installable Extensible SDK Content</title> |