summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/sdk-extensible.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-05-31 14:26:47 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-06-15 11:26:46 +0100
commit4d586da1083d70b0d370310d4dd05f6b1b391a62 (patch)
treef591623ac6315d6e930ae29b341784b1fc4a50b1 /documentation/sdk-manual/sdk-extensible.xml
parentbf2a7a31ca2e0318b035997e2f0fa5ea2b2b9b68 (diff)
downloadpoky-4d586da1083d70b0d370310d4dd05f6b1b391a62.tar.gz
sdk-manual: Edits to "Creating a Derivative SDK With Additional Components"
Fixed some poor writing in this section. (From yocto-docs rev: 5709c2c2c1c37166ec5df1193b58ff82bb10b4c3) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual/sdk-extensible.xml')
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml35
1 files changed, 19 insertions, 16 deletions
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml
index a586e3cdb5..5215a9d096 100644
--- a/documentation/sdk-manual/sdk-extensible.xml
+++ b/documentation/sdk-manual/sdk-extensible.xml
@@ -1749,31 +1749,34 @@
1749 1749
1750 <para> 1750 <para>
1751 You might need to produce an SDK that contains your own custom 1751 You might need to produce an SDK that contains your own custom
1752 libraries for sending to a third party (e.g., if you are a vendor with 1752 libraries.
1753 customers needing to build their own software for the target platform). 1753 A good example would be if you were a vendor with customers that
1754 If that is the case, then you can produce a derivative SDK based on 1754 use your SDK to build their own platform-specific software and
1755 the currently installed SDK fairly easily. 1755 those customers need an SDK that has custom libraries.
1756 Use these steps: 1756 In such a case, you can produce a derivative SDK based on the
1757 currently installed SDK fairly easily by following these steps:
1757 <orderedlist> 1758 <orderedlist>
1758 <listitem><para>If necessary, install an extensible SDK that 1759 <listitem><para>
1760 If necessary, install an extensible SDK that
1759 you want to use as a base for your derivative SDK. 1761 you want to use as a base for your derivative SDK.
1760 </para></listitem> 1762 </para></listitem>
1761 <listitem><para>Source the environment script for the SDK. 1763 <listitem><para>
1764 Source the environment script for the SDK.
1762 </para></listitem> 1765 </para></listitem>
1763 <listitem><para>Add the extra libraries or other components 1766 <listitem><para>
1764 you want by using the <filename>devtool add</filename> 1767 Add the extra libraries or other components you want by
1765 command. 1768 using the <filename>devtool add</filename> command.
1766 </para></listitem> 1769 </para></listitem>
1767 <listitem><para>Run the <filename>devtool build-sdk</filename> 1770 <listitem><para>
1768 command. 1771 Run the <filename>devtool build-sdk</filename> command.
1769 </para></listitem> 1772 </para></listitem>
1770 </orderedlist> 1773 </orderedlist>
1771 The above procedure takes the recipes added to the workspace and 1774 The previous steps take the recipes added to the workspace and
1772 constructs a new SDK installer containing those recipes and the 1775 construct a new SDK installer that contains those recipes and the
1773 resulting binary artifacts. 1776 resulting binary artifacts.
1774 The recipes go into their own separate layer in the constructed 1777 The recipes go into their own separate layer in the constructed
1775 derivative SDK, leaving the workspace clean and ready for users 1778 derivative SDK, which leaves the workspace clean and ready for
1776 to add their own recipes. 1779 users to add their own recipes.
1777 </para> 1780 </para>
1778 </section> 1781 </section>
1779</chapter> 1782</chapter>