summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/sdk-manual')
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml26
1 files changed, 13 insertions, 13 deletions
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml
index bc77bed86c..a586e3cdb5 100644
--- a/documentation/sdk-manual/sdk-extensible.xml
+++ b/documentation/sdk-manual/sdk-extensible.xml
@@ -1681,16 +1681,14 @@
1681 <title>Installing Additional Items Into the Extensible SDK</title> 1681 <title>Installing Additional Items Into the Extensible SDK</title>
1682 1682
1683 <para> 1683 <para>
1684 The extensible SDK typically only comes with a small number of tools 1684 Out of the box the extensible SDK typically only comes with a small
1685 and libraries out of the box. 1685 number of tools and libraries.
1686 If you have a minimal SDK, then it starts mostly empty and is 1686 A minimal SDK starts mostly empty and is populated on-demand.
1687 populated on-demand. 1687 Sometimes you must explicitly install extra items into the SDK.
1688 However, sometimes you will need to explicitly install extra items
1689 into the SDK.
1690 If you need these extra items, you can first search for the items 1688 If you need these extra items, you can first search for the items
1691 using the <filename>devtool search</filename> command. 1689 using the <filename>devtool search</filename> command.
1692 For example, suppose you need to link to libGL but you are not sure 1690 For example, suppose you need to link to libGL but you are not sure
1693 which recipe provides it. 1691 which recipe provides libGL.
1694 You can use the following command to find out: 1692 You can use the following command to find out:
1695 <literallayout class='monospaced'> 1693 <literallayout class='monospaced'>
1696 $ devtool search libGL 1694 $ devtool search libGL
@@ -1701,17 +1699,19 @@
1701 <literallayout class='monospaced'> 1699 <literallayout class='monospaced'>
1702 $ devtool sdk-install mesa 1700 $ devtool sdk-install mesa
1703 </literallayout> 1701 </literallayout>
1704 By default, the <filename>devtool sdk-install</filename> assumes the 1702 By default, the <filename>devtool sdk-install</filename> command
1705 item is available in pre-built form from your SDK provider. 1703 assumes the item is available in pre-built form from your SDK
1704 provider.
1706 If the item is not available and it is acceptable to build the item 1705 If the item is not available and it is acceptable to build the item
1707 from source, you can add the "-s" option as follows: 1706 from source, you can add the "-s" option as follows:
1708 <literallayout class='monospaced'> 1707 <literallayout class='monospaced'>
1709 $ devtool sdk-install -s mesa 1708 $ devtool sdk-install -s mesa
1710 </literallayout> 1709 </literallayout>
1711 It is important to remember that building the item from source takes 1710 It is important to remember that building the item from source
1712 significantly longer than installing the pre-built artifact. 1711 takes significantly longer than installing the pre-built artifact.
1713 Also, if no recipe exists for the item you want to add to the SDK, you 1712 Also, if no recipe exists for the item you want to add to the SDK,
1714 must instead add it using the <filename>devtool add</filename> command. 1713 you must instead add the item using the
1714 <filename>devtool add</filename> command.
1715 </para> 1715 </para>
1716 </section> 1716 </section>
1717 1717