summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-start.xml38
1 files changed, 19 insertions, 19 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index 02f6bd0452..092039368c 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -72,10 +72,10 @@
72 <listitem><para><emphasis>Packages:</emphasis> The OpenEmbedded build system 72 <listitem><para><emphasis>Packages:</emphasis> The OpenEmbedded build system
73 requires certain packages exist on your development system (e.g. Python 2.6 or 2.7). 73 requires certain packages exist on your development system (e.g. Python 2.6 or 2.7).
74 See "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" 74 See "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>"
75 section in the Yocto Project Quick Start and the 75 section in the Yocto Project Quick Start and the
76 "<ulink url='&YOCTO_DOCS_REF_URL;#required-packages-for-the-host-development-system'>Required Packages for the Host Development System</ulink>" 76 "<ulink url='&YOCTO_DOCS_REF_URL;#required-packages-for-the-host-development-system'>Required Packages for the Host Development System</ulink>"
77 section in the Yocto Project Reference Manual for the exact 77 section in the Yocto Project Reference Manual for the exact
78 package requirements and the installation commands to install 78 package requirements and the installation commands to install
79 them for the supported distributions. 79 them for the supported distributions.
80 </para></listitem> 80 </para></listitem>
81 <listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis> 81 <listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis>
@@ -88,14 +88,14 @@
88 hierarchical set of files as the "Source Directory." 88 hierarchical set of files as the "Source Directory."
89 </note> 89 </note>
90 <itemizedlist> 90 <itemizedlist>
91 <listitem><para><emphasis>Tarball Extraction:</emphasis> 91 <listitem><para><emphasis>Tarball Extraction:</emphasis>
92 If you are not going to contribute back into the Yocto 92 If you are not going to contribute back into the Yocto
93 Project, you can simply go to the 93 Project, you can simply go to the
94 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>, 94 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>,
95 select the "Downloads" tab, and choose what you want. 95 select the "Downloads" tab, and choose what you want.
96 Once you have the tarball, just extract it into a 96 Once you have the tarball, just extract it into a
97 directory of your choice.</para> 97 directory of your choice.</para>
98 <para>For example, the following command extracts the 98 <para>For example, the following command extracts the
99 Yocto Project &DISTRO; release tarball 99 Yocto Project &DISTRO; release tarball
100 into the current working directory and sets up the local Source Directory 100 into the current working directory and sets up the local Source Directory
101 with a top-level folder named <filename>&YOCTO_POKY;</filename>: 101 with a top-level folder named <filename>&YOCTO_POKY;</filename>:
@@ -126,7 +126,7 @@
126 remote: Compressing objects: 100% (47428/47428), done. 126 remote: Compressing objects: 100% (47428/47428), done.
127 remote: Total 183981 (delta 132271), reused 183703 (delta 132044) 127 remote: Total 183981 (delta 132271), reused 183703 (delta 132044)
128 Receiving objects: 100% (183981/183981), 89.71 MiB | 2.93 MiB/s, done. 128 Receiving objects: 100% (183981/183981), 89.71 MiB | 2.93 MiB/s, done.
129 Resolving deltas: 100% (132271/132271), done. 129 Resolving deltas: 100% (132271/132271), done.
130 </literallayout></para> 130 </literallayout></para>
131 <para>For another example of how to set up your own local Git repositories, see this 131 <para>For another example of how to set up your own local Git repositories, see this
132 <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'> 132 <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
@@ -168,9 +168,9 @@
168 Cloning into 'my-linux-yocto-3.8-work'... 168 Cloning into 'my-linux-yocto-3.8-work'...
169 done. 169 done.
170 </literallayout></para></listitem> 170 </literallayout></para></listitem>
171 <listitem id='poky-extras-repo'><para><emphasis> 171 <listitem id='meta-yocto-kernel-extras-repo'><para><emphasis>
172 The <filename>poky-extras</filename> Git Repository</emphasis>: 172 The <filename>meta-yocto-kernel-extras</filename> Git Repository</emphasis>:
173 The <filename>poky-extras</filename> Git repository contains Metadata needed 173 The <filename>meta-yocto-kernel-extras</filename> Git repository contains Metadata needed
174 only if you are modifying and building the kernel image. 174 only if you are modifying and building the kernel image.
175 In particular, it contains the kernel BitBake append (<filename>.bbappend</filename>) 175 In particular, it contains the kernel BitBake append (<filename>.bbappend</filename>)
176 files that you 176 files that you
@@ -178,17 +178,17 @@
178 image. 178 image.
179 Pointing to these local files is much more efficient than requiring a download of the 179 Pointing to these local files is much more efficient than requiring a download of the
180 kernel's source files from upstream each time you make changes to the kernel.</para> 180 kernel's source files from upstream each time you make changes to the kernel.</para>
181 <para>You can find the <filename>poky-extras</filename> Git Repository in the 181 <para>You can find the <filename>meta-yocto-kernel-extras</filename> Git Repository in the
182 "Yocto Metadata Layers" area of the Yocto Project Source Repositories at 182 "Yocto Metadata Layers" area of the Yocto Project Source Repositories at
183 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>. 183 <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>.
184 It is good practice to create this Git repository inside the Source Directory.</para> 184 It is good practice to create this Git repository inside the Source Directory.</para>
185 <para>Following is an example that creates the <filename>poky-extras</filename> Git 185 <para>Following is an example that creates the <filename>meta-yocto-kernel-extras</filename> Git
186 repository inside the Source Directory, which is named <filename>poky</filename> 186 repository inside the Source Directory, which is named <filename>poky</filename>
187 in this case: 187 in this case:
188 <literallayout class='monospaced'> 188 <literallayout class='monospaced'>
189 $ cd ~/poky 189 $ cd ~/poky
190 $ git clone git://git.yoctoproject.org/poky-extras poky-extras 190 $ git clone git://git.yoctoproject.org/meta-yocto-kernel-extras meta-yocto-kernel-extras
191 Cloning into 'poky-extras'... 191 Cloning into 'meta-yocto-kernel-extras'...
192 remote: Counting objects: 690, done. 192 remote: Counting objects: 690, done.
193 remote: Compressing objects: 100% (431/431), done. 193 remote: Compressing objects: 100% (431/431), done.
194 remote: Total 690 (delta 238), reused 690 (delta 238) 194 remote: Total 690 (delta 238), reused 690 (delta 238)
@@ -223,10 +223,10 @@
223 information on BSP Layers. 223 information on BSP Layers.
224 <itemizedlist> 224 <itemizedlist>
225 <listitem><para><emphasis>Tarball Extraction:</emphasis> You can download any released 225 <listitem><para><emphasis>Tarball Extraction:</emphasis> You can download any released
226 BSP tarball from the same "Downloads" page of the 226 BSP tarball from the same "Downloads" page of the
227 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink> 227 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>
228 to get the Yocto Project release. 228 to get the Yocto Project release.
229 Once on the "Download" page, look for "BSP" under the 229 Once on the "Download" page, look for "BSP" under the
230 "Type" heading.</para> 230 "Type" heading.</para>
231 <para>Once you have the tarball, just extract it into a directory of your choice. 231 <para>Once you have the tarball, just extract it into a directory of your choice.
232 Again, this method just produces a snapshot of the BSP layer in the form 232 Again, this method just produces a snapshot of the BSP layer in the form