mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-07-16 15:57:04 +00:00
Code Issues Projects Releases Wiki Activity

sdk-manual: Updates to sections for updating installed Ext SDKs

Browse Source 
There are two sections that deal with this topic.  One is from the
standpoint of a user using a 3rd party published and installed
extensible SDK ("Applying Updates to an Installed Extensible SDK").
The other is from the standpoint of a person providing Extensible
SDKs for consumption ("Providing Updates to the Extensible SDK
After Installation").  These sections needed some closer examination
regarding fully describing what was going on.  I provided some
re-writes to both.

(From yocto-docs rev: 1c60b13b5f1813d6e3688e1efce32b7f31422e86)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-07-16 14:28:52 -07:00
committed by Richard Purdie
parent 6cb9fddcab
commit 3b374b09df
2 changed files with 29 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/sdk-manual/sdk-appendix-customizing.xml
+13 -8
View File
@@ -213,12 +213,14 @@
<para>
When you make changes to your configuration or to the metadata and
if you want those changes to be reflected in installed SDKs, you need
to perform additional steps to make it possible for those that use
the SDK to update their installations with the
to perform additional steps.
These steps make it possible for anyone using the installed SDKs to
update the installed SDKs by using the
<filename>devtool sdk-update</filename> command:
<orderedlist>
<listitem><para>
Create a directory that can be shared over HTTP or HTTPS.
This directory will contain the published SDK.
</para></listitem>
<listitem><para>
Set the
@@ -226,7 +228,10 @@
variable to point to the corresponding HTTP or HTTPS URL.
Setting this variable causes any SDK built to default to that
URL and thus, the user does not have to pass the URL to the
<filename>devtool sdk-update</filename> command.
<filename>devtool sdk-update</filename> command as described
in the
"<link linkend='sdk-applying-updates-to-an-installed-extensible-sdk'>Applying Updates to an Installed Extensible SDK</link>"
section.
</para></listitem>
<listitem><para>
Build the extensible SDK normally (i.e., use the
@@ -236,7 +241,7 @@
<listitem><para>
Publish the SDK using the following command:
<literallayout class='monospaced'>
$ oe-publish-sdk <replaceable>some_path</replaceable>/sdk-installer.sh <replaceable>path_to_shared/http_directory</replaceable>
$ oe-publish-sdk <replaceable>some_path</replaceable>/sdk-installer.sh <replaceable>path_to_shared_http_directory</replaceable>
</literallayout>
You must repeat this step each time you rebuild the SDK
with changes that you want to make available through the
@@ -246,11 +251,11 @@
</para>
<para>
Completing the above steps allows users of the existing SDKs to
simply run <filename>devtool sdk-update</filename> to retrieve the
latest updates.
Completing the above steps allows users of the existing installed
SDKs to simply run <filename>devtool sdk-update</filename> to
retrieve and apply the latest updates.
See the
"<link linkend='sdk-updating-the-extensible-sdk'>Updating the Extensible SDK</link>"
"<link linkend='sdk-applying-updates-to-an-installed-extensible-sdk'>Applying Updates to an Installed Extensible SDK</link>"
section for further information.
</para>
</section>