mirror of
https://git.yoctoproject.org/poky
synced 2026-05-01 06:32:11 +02:00
sdk-manual: Edits to "Installing Additional Items Into the Extensible SDK"
Minor edits. (From yocto-docs rev: 3ed2c1026bf03feb03001e00daec55b94d7dc35b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
73d00d17fb
commit
bf2a7a31ca
@@ -1681,16 +1681,14 @@
|
|||||||
<title>Installing Additional Items Into the Extensible SDK</title>
|
<title>Installing Additional Items Into the Extensible SDK</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The extensible SDK typically only comes with a small number of tools
|
Out of the box the extensible SDK typically only comes with a small
|
||||||
and libraries out of the box.
|
number of tools and libraries.
|
||||||
If you have a minimal SDK, then it starts mostly empty and is
|
A minimal SDK starts mostly empty and is populated on-demand.
|
||||||
populated on-demand.
|
Sometimes you must explicitly install extra items into the SDK.
|
||||||
However, sometimes you will need to explicitly install extra items
|
|
||||||
into the SDK.
|
|
||||||
If you need these extra items, you can first search for the items
|
If you need these extra items, you can first search for the items
|
||||||
using the <filename>devtool search</filename> command.
|
using the <filename>devtool search</filename> command.
|
||||||
For example, suppose you need to link to libGL but you are not sure
|
For example, suppose you need to link to libGL but you are not sure
|
||||||
which recipe provides it.
|
which recipe provides libGL.
|
||||||
You can use the following command to find out:
|
You can use the following command to find out:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ devtool search libGL
|
$ devtool search libGL
|
||||||
@@ -1701,17 +1699,19 @@
|
|||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ devtool sdk-install mesa
|
$ devtool sdk-install mesa
|
||||||
</literallayout>
|
</literallayout>
|
||||||
By default, the <filename>devtool sdk-install</filename> assumes the
|
By default, the <filename>devtool sdk-install</filename> command
|
||||||
item is available in pre-built form from your SDK provider.
|
assumes the item is available in pre-built form from your SDK
|
||||||
|
provider.
|
||||||
If the item is not available and it is acceptable to build the item
|
If the item is not available and it is acceptable to build the item
|
||||||
from source, you can add the "-s" option as follows:
|
from source, you can add the "-s" option as follows:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ devtool sdk-install -s mesa
|
$ devtool sdk-install -s mesa
|
||||||
</literallayout>
|
</literallayout>
|
||||||
It is important to remember that building the item from source takes
|
It is important to remember that building the item from source
|
||||||
significantly longer than installing the pre-built artifact.
|
takes significantly longer than installing the pre-built artifact.
|
||||||
Also, if no recipe exists for the item you want to add to the SDK, you
|
Also, if no recipe exists for the item you want to add to the SDK,
|
||||||
must instead add it using the <filename>devtool add</filename> command.
|
you must instead add the item using the
|
||||||
|
<filename>devtool add</filename> command.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user