mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-20 03:49:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

sdk-manual: WIP - Various small edits as WIP

Browse Source 
(From yocto-docs rev: 53c16de81028d5564a75b4787203d6862258f68e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2016-01-25 15:14:57 -08:00
committed by Richard Purdie
parent f15f96c07e
commit 890f7215f0
4 changed files with 128 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
documentation/sdk-manual/sdk-using.xml
View File

@@ -7,20 +7,58 @@
<title>Using the Standard SDK</title>
<para>
This chapter is going to cover all the SDK stuff that is common
to both the SDK and the extensible SDK.
This chapter describes how to use a standard SDK.
Information covers installing the SDK and task-based procedures common
for developing with a standard SDK.
<note>
The tasks you can perform using a standard SDK are also applicable
when you are using an extensible SDK.
For information on the differences when using an extensible SDK as
compared to an extensible SDK, see the
"<link linkend='sdk-extensible'>Using the Extensible SDK</link>"
chapter.
</note>
</para>
<section id='sdk-setting-up-to-use-the-standard-sdk'>
<title>Setting Up to Use the Standard SDK</title>
<para>
What do you need to use the SDK?
What does your system have to have on it?
What are the recommendations?
What conditions in your development scenario warrant use of just the
standard SDK as compared to the extensible SDK?
Show any specific procedures needed to get set up to use the SDK.
Here is a list of items I think need addressed in this section:
<itemizedlist>
<listitem><para><emphasis>What is your situation?</emphasis></para>
<para>In other words, is the developer on a machine that
has YP on it?
Are they on a machine that does not?
Is the image they are developing against available as a
pre-built, down-loadable image and can they get it?</para>
<para>Depending on the scenario, there are different ways
to make sure the machine they are using is ready to use a
standard SDK.
I think we need to cover the various situations in this
section.
</para></listitem>
<listitem><para><emphasis>What are the recommendations?</emphasis></para>
<para>What is the most common development scenario?
Is there a recommended development flow we want to present
when using a standard SDK?
What conditions in a development scenario warrant use of
just the standard SDK as compared to the extensible SDK?
</para></listitem>
<listitem><para><emphasis>What procedures do we want to cover to set up
the standard SDK?</emphasis></para>
<para>There is a ton of setup information in the
current ADT manual regarding getting, building, and installing
an SDK.
We would ignore the stuff about the ADT installer script
since I presume that is going away.
But, there are steps to download and existing
<filename>.sh</filename> install script, build out the
toolchains assuming your system has YP on it and you can run
BitBake, getting the root filesystem, getting an image so you
run QEMU on your system, etc.
</para></listitem>
</itemizedlist>
</para>
</section>