mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 01:19:52 +00:00
Code Issues Projects Releases Wiki Activity

sdk-manual: Edits to "Creating a Derivative SDK With Additional Components"

Browse Source 
Fixed some poor writing in this section.

(From yocto-docs rev: ed59c0e30d6c093f0dda54c0d61a2863a7e826e0)

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-05-31 14:26:47 -07:00
committed by Richard Purdie
parent 18658481ef
commit 3286f68185
1 changed files with 19 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/sdk-manual/sdk-extensible.xml
+19 -16
View File
@@ -1749,31 +1749,34 @@
<para> <para>
You might need to produce an SDK that contains your own custom You might need to produce an SDK that contains your own custom
libraries for sending to a third party (e.g., if you are a vendor with libraries.
customers needing to build their own software for the target platform). A good example would be if you were a vendor with customers that
If that is the case, then you can produce a derivative SDK based on use your SDK to build their own platform-specific software and
the currently installed SDK fairly easily. those customers need an SDK that has custom libraries.
Use these steps: In such a case, you can produce a derivative SDK based on the
currently installed SDK fairly easily by following these steps:
<orderedlist> <orderedlist>
<listitem><para>If necessary, install an extensible SDK that <listitem><para>
If necessary, install an extensible SDK that
you want to use as a base for your derivative SDK. you want to use as a base for your derivative SDK.
</para></listitem> </para></listitem>
<listitem><para>Source the environment script for the SDK. <listitem><para>
Source the environment script for the SDK.
</para></listitem> </para></listitem>
<listitem><para>Add the extra libraries or other components <listitem><para>
you want by using the <filename>devtool add</filename> Add the extra libraries or other components you want by
command. using the <filename>devtool add</filename> command.
</para></listitem> </para></listitem>
<listitem><para>Run the <filename>devtool build-sdk</filename> <listitem><para>
command. Run the <filename>devtool build-sdk</filename> command.
</para></listitem> </para></listitem>
</orderedlist> </orderedlist>
The above procedure takes the recipes added to the workspace and The previous steps take the recipes added to the workspace and
constructs a new SDK installer containing those recipes and the construct a new SDK installer that contains those recipes and the
resulting binary artifacts. resulting binary artifacts.
The recipes go into their own separate layer in the constructed The recipes go into their own separate layer in the constructed
derivative SDK, leaving the workspace clean and ready for users derivative SDK, which leaves the workspace clean and ready for
to add their own recipes. users to add their own recipes.
</para> </para>
</section> </section>
</chapter> </chapter>