documentation/dev-manual/dev-manual-start.xml: Edits to clarify YP files

I have a new understanding of the files resulting from setting up
Git repos as compared to getting files from tarballs.  I changed
some wordings to help make those distinctions.

(From yocto-docs rev: b7ba9df07cf9d64f61ac73e501c253c42570970d)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2011-07-22 08:40:12 -07:00
committed by Richard Purdie
parent af22a8c671
commit fed0630941

View File

@@ -62,19 +62,22 @@
<listitem><para><emphasis>Tarball Extraction:</emphasis> If you are not going to contribute
back into the Yocto Project you can simply download the Yocto Project release you want
from the websites <ulink url='http://yoctoproject.org/download'>download page</ulink>.
Once you have the tarball, just extract it into a directory of your choice.
Once you have the tarball, just extract it into a directory of your choice.
This method does not produce a <filename>poky</filename> Git repository.
You end up simply with a snapshot of Yocto Project files that are based on the
particular release in the tarball.
If you are interested in supported Board Support Packages (BSPs) you can also download
these release tarballs from the same site and locate them in a directory of your
choice.</para></listitem>
<listitem><para><emphasis>Git Method:</emphasis> If you are going to be contributing
<listitem><para><emphasis>Git Repository Method:</emphasis> If you are going to be contributing
back into the Yocto Project you should probably use Git commands to set up a local
Git repository of the Yocto Project.
Doing so creates a history of changes you might make and allows you to easily submit
changes upstream to the project.
For an example of how to set up your own local Git repository of Yocto Project,
see this
<filename>poky</filename> Git repository of from the Yocto Project.
Doing so creates a Git repository with a complete history of changes and allows
you to easily submit your changes upstream to the project.
For an example of how to set up your own local Git repositories see this
<ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
wiki page</ulink>, which covers checking out the Yocto sources.</para></listitem>
wiki page</ulink>, which describes how to create both <filename>poky</filename>
and <filename>meta-intel</filename> Git repositories.</para></listitem>
</itemizedlist></para></listitem>
<listitem><para><emphasis>Supported Board Support Packages (BSPs):</emphasis> The same considerations
exist for BSPs.
@@ -83,11 +86,18 @@
<listitem><para><emphasis>Tarball Extraction:</emphasis> You can download any released
BSP tarball from the same
<ulink url='http://yoctoproject.org/download'>download site</ulink>.
Once you have the tarball just extract it into a directory of your choice.</para></listitem>
<listitem><para><emphasis>Git Method:</emphasis> For an example of how to integrate
the metadata for BSPs into your local Yocto Project Git repository see this
Once you have the tarball just extract it into a directory of your choice.
Again, this method just produces a snapshot of the BSP layer in the form
of a hierarchical directory structure.</para></listitem>
<listitem><para><emphasis>Git Repository Method:</emphasis> If you are working
with a <filename>poky</filename> Git repository you should also set up a
<filename>meta-intel</filename> Git repository.
Typically, you set up the <filename>meta-intel</filename> Git repository inside
the <filename>poky</filename> Git repository.
The same
<ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
wiki page</ulink>, which covers how to check out the meta-intel repository.</para></listitem>
wiki page</ulink> referenced earlier covers how to
set up the <filename>meta-intel</filename> Git repository.</para></listitem>
</itemizedlist></para></listitem>
<listitem><para><emphasis>Eclipse Yocto Plug-in:</emphasis> If you are developing using the
Eclipse Integrated Development Environment (IDE) you will need this plug-in.