diff options
-rw-r--r-- | documentation/dev-manual/dev-manual-bsp-appendix.xml | 48 |
1 files changed, 4 insertions, 44 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index f3927c35d2..84fb541598 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml | |||
@@ -18,55 +18,15 @@ | |||
18 | </itemizedlist> | 18 | </itemizedlist> |
19 | </para> | 19 | </para> |
20 | 20 | ||
21 | <section id='setting-up-yocto-project-app'> | 21 | <section id='getting-local-yocto-project-files-and-bsp-files'> |
22 | <title>Setting Up Yocto Project</title> | 22 | <title>Getting Local Yocto Project Files and BSP Files</title> |
23 | 23 | ||
24 | <para> | 24 | <para> |
25 | You need to have the Yocto Project files available on your host system. | 25 | You need to have the Yocto Project files available on your host system. |
26 | You can get files through tarball extraction or by cloning the <filename>poky</filename> | 26 | You can get files through tarball extraction or by cloning the <filename>poky</filename> |
27 | Git repository. | 27 | Git repository. |
28 | Typically, cloning the Git repository is the method to use. | 28 | See the <xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual |
29 | This allows you to maintain a complete history of changes and facilitates you | 29 | for information on how to get these files. |
30 | contributing back to the Yocto Project. | ||
31 | However, if you just want a hierarchical file structure that contains the recipes | ||
32 | and metadata that let you develop you can download tarballs from the | ||
33 | <ulink url='http://yoctoproject.org/download'>download page</ulink>. | ||
34 | </para> | ||
35 | |||
36 | <para> | ||
37 | Regardless of the method you use this manual will refer to the resulting | ||
38 | hierarchical set of files as "the local Yocto Project files." | ||
39 | </para> | ||
40 | |||
41 | <para> | ||
42 | [WRITER'S NOTE: I need to substitute correct and actual filenames for the | ||
43 | 1.1 release throughout this example once they become available.] | ||
44 | </para> | ||
45 | |||
46 | <para> | ||
47 | If you download a tarball you can extract it into any directory you want using the | ||
48 | tar command. | ||
49 | For example, the following command extracts the Yocto Project 1.1 release tarball | ||
50 | into the current working directory and sets up a file structure whose top-level | ||
51 | directory is named <filename>poky-1.1</filename>: | ||
52 | <literallayout class='monospaced'> | ||
53 | $ tar xfj poky-1.1.tar.bz2 | ||
54 | </literallayout> | ||
55 | </para> | ||
56 | |||
57 | <para> | ||
58 | The following transcript shows how to clone the <filename>poky</filename> Git repository | ||
59 | into the current working directory. | ||
60 | The command creates the repository in a directory named <filename>poky</filename>: | ||
61 | <literallayout class='monospaced'> | ||
62 | $ git clone git://git.yoctoproject.org/poky | ||
63 | Initialized empty Git repository in /home/scottrif/poky/.git/ | ||
64 | remote: Counting objects: 107624, done. | ||
65 | remote: Compressing objects: 100% (37128/37128), done. | ||
66 | remote: Total 107624 (delta 73393), reused 99851 (delta 67287) | ||
67 | Receiving objects: 100% (107624/107624), 69.74 MiB | 483 KiB/s, done. | ||
68 | Resolving deltas: 100% (73393/73393), done. | ||
69 | </literallayout> | ||
70 | </para> | 30 | </para> |
71 | 31 | ||
72 | <para> | 32 | <para> |