diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-02-15 10:02:27 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-02-15 10:02:27 +0000 |
commit | 21c112ca49407eac9808355ed286c51e26d59580 (patch) | |
tree | 2805e244a2416dc2cfe40703c999c36d086ee05c | |
parent | e5e02f3cba1b81af39f432730802e871deb53eca (diff) | |
parent | 647aaad6fb8b9c22c5287d387cb1fb691a7bd5ee (diff) | |
download | poky-21c112ca49407eac9808355ed286c51e26d59580.tar.gz |
Merge branch 'srifenbark/docs' of ssh://git.pokylinux.org/poky-contrib
-rw-r--r-- | documentation/kernel-manual/kernel-how-to.xml | 33 | ||||
-rw-r--r-- | documentation/yocto-project-qs/yocto-project-qs.xml | 11 |
2 files changed, 30 insertions, 14 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml index 6b326b5561..c3c9569adf 100644 --- a/documentation/kernel-manual/kernel-how-to.xml +++ b/documentation/kernel-manual/kernel-how-to.xml | |||
@@ -882,7 +882,7 @@ repository. | |||
882 | The following commands illustrate how you can condense and merge two BSPs into a second SCM: | 882 | The following commands illustrate how you can condense and merge two BSPs into a second SCM: |
883 | <literallayout class='monospaced'> | 883 | <literallayout class='monospaced'> |
884 | > git checkout common_pc-standard | 884 | > git checkout common_pc-standard |
885 | > git merge cav_ebt5800-standard | 885 | > git merge common_pc_64-standard |
886 | # resolve any conflicts and commit them | 886 | # resolve any conflicts and commit them |
887 | > cd .. ; echo linux/.git > .cvsignore | 887 | > cd .. ; echo linux/.git > .cvsignore |
888 | > cvs import -m "initial import" linux MY_COMPANY start | 888 | > cvs import -m "initial import" linux MY_COMPANY start |
@@ -1054,7 +1054,7 @@ That's it. Configure and build. | |||
1054 | For this example the only thing left was the kernel directory with a | 1054 | For this example the only thing left was the kernel directory with a |
1055 | <filename>linux-yocto_git.bbappend</filename> file (linux-yocto is the kernel listed in | 1055 | <filename>linux-yocto_git.bbappend</filename> file (linux-yocto is the kernel listed in |
1056 | <filename>meta-crownbay/conf/machine/crownbay.conf</filename></para></listitem>. | 1056 | <filename>meta-crownbay/conf/machine/crownbay.conf</filename></para></listitem>. |
1057 | <listitem><para>Add a new entry in the <filename>build/donf/bblayers.conf</filename> | 1057 | <listitem><para>Add a new entry in the <filename>build/conf/bblayers.conf</filename> |
1058 | so the new layer can be found by Bitbake.</para></listitem> | 1058 | so the new layer can be found by Bitbake.</para></listitem> |
1059 | </itemizedlist> | 1059 | </itemizedlist> |
1060 | </para></listitem> | 1060 | </para></listitem> |
@@ -1088,21 +1088,26 @@ That's it. Configure and build. | |||
1088 | </para></listitem> | 1088 | </para></listitem> |
1089 | 1089 | ||
1090 | <listitem><para> | 1090 | <listitem><para> |
1091 | Point the build at the new kernel git tree. | 1091 | In a layer, create a <filename>linux-yocto_git.bbappend</filename> |
1092 | </para> | 1092 | file with the following: |
1093 | </para> | ||
1093 | 1094 | ||
1094 | <para> | 1095 | <para> |
1095 | You can do this by commenting out the SRC_URI variable in | ||
1096 | <filename>meta/recipes-kernel/linux/linux-yocto_git.bb</filename> and using a SRC_URI | ||
1097 | that points to your new bare git tree. | ||
1098 | You should also be able to do this in <filename>linux-yocto_git.bbappend</filename> in the layer: | ||
1099 | <literallayout class='monospaced'> | 1096 | <literallayout class='monospaced'> |
1100 | # To use a staged, on-disk bare clone of a Wind River Kernel, use a variant of the | 1097 | COMPATIBLE_MACHINE = ${MACHINE} |
1101 | # below SRC_URI = "git://///path/to/kernel/default_kernel.git;fullclone=1" | 1098 | |
1102 | # | 1099 | # It is often nice to have a local clone of the kernel repository, to |
1103 | SRC_URI = "git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=${KBRANCH};name=machine | 1100 | # allow patches to be staged, branches created, and so forth. Modify |
1104 | \ | 1101 | # KSRC to point to your local clone as appropriate. |
1105 | git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;noclone=1;branch=wrs_meta;name=meta" | 1102 | |
1103 | # KSRC ?= /path/to/your/bare/clone/yocto-kernel | ||
1104 | |||
1105 | # KMACHINE is the branch to be built, or alternateively | ||
1106 | # KBRANCH can be directly set. | ||
1107 | |||
1108 | # KBRANCH ?= "${KMACHINE}-${LINUX_KERNEL_TYPE}" | ||
1109 | |||
1110 | # SRC_URI = "git://${KSRC};nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" | ||
1106 | </literallayout> | 1111 | </literallayout> |
1107 | </para> | 1112 | </para> |
1108 | 1113 | ||
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 24480bc787..56dafe5e0a 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml | |||
@@ -234,6 +234,17 @@ | |||
234 | $ source poky-laverne-4.0/poky-init-build-env poky-4.0-build | 234 | $ source poky-laverne-4.0/poky-init-build-env poky-4.0-build |
235 | </literallayout> | 235 | </literallayout> |
236 | </para> | 236 | </para> |
237 | |||
238 | <tip><para> | ||
239 | To help conserve disk space during builds you can add the following statement | ||
240 | to your <filename>local.conf</filename> file. | ||
241 | Adding this statement deletes the work directory used for building a package | ||
242 | once the package is built. | ||
243 | <literallayout class='monospaced'> | ||
244 | INHERIT += "rm_work" | ||
245 | </literallayout> | ||
246 | </para></tip> | ||
247 | |||
237 | <itemizedlist> | 248 | <itemizedlist> |
238 | <listitem><para>The first two commands extract the Yocto Project files from the | 249 | <listitem><para>The first two commands extract the Yocto Project files from the |
239 | release tarball and place them into a subdirectory of your current directory.</para></listitem> | 250 | release tarball and place them into a subdirectory of your current directory.</para></listitem> |