From fed0630941ca8cc13dac7ecc68ee3b806786a61c Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 22 Jul 2011 08:40:12 -0700 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-start.xml | 34 +++++++++++++++++---------- 1 file changed, 22 insertions(+), 12 deletions(-) (limited to 'documentation/dev-manual/dev-manual-start.xml') diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 5dbe0ed4da..a60f256142 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -62,19 +62,22 @@ Tarball Extraction: If you are not going to contribute back into the Yocto Project you can simply download the Yocto Project release you want from the website’s download page. - 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 poky 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. - Git Method: If you are going to be contributing + Git Repository Method: 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 + poky 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 - wiki page, which covers checking out the Yocto sources. + wiki page, which describes how to create both poky + and meta-intel Git repositories. Supported Board Support Packages (BSPs): The same considerations exist for BSPs. @@ -83,11 +86,18 @@ Tarball Extraction: You can download any released BSP tarball from the same download site. - Once you have the tarball just extract it into a directory of your choice. - Git Method: 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. + Git Repository Method: If you are working + with a poky Git repository you should also set up a + meta-intel Git repository. + Typically, you set up the meta-intel Git repository inside + the poky Git repository. + The same - wiki page, which covers how to check out the meta-intel repository. + wiki page referenced earlier covers how to + set up the meta-intel Git repository. Eclipse Yocto Plug-in: If you are developing using the Eclipse Integrated Development Environment (IDE) you will need this plug-in. -- cgit v1.2.3-54-g00ecf