diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-03-18 17:02:37 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-25 12:29:42 +0000 |
| commit | 24ee5fa913104cba01c796559bf3e5315f7c1722 (patch) | |
| tree | d2038d8bdaac920516ba12fcf64490db27147d6f | |
| parent | fceba79bf76a5ab4ddd365f90ea847a15a44bc01 (diff) | |
| download | poky-24ee5fa913104cba01c796559bf3e5315f7c1722.tar.gz | |
dev-manual: Added yocto-layer script note and updated kernel version
I added a bit about the layer creation in the patching the kernel
section. The example does it by hand and now you could obviously
use the yocto-layer create script. I made a note of saying the
example does it by hand.
Also, in the menuconfig example. I updated the kernel version from
3.4 to 3.14. It was very old.
(From yocto-docs rev: 2696d4e45bccbb910c3d721e3f1d46d48309ee6d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 27 |
1 files changed, 21 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 4319ff061a..ef801d616d 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
| @@ -2989,7 +2989,7 @@ | |||
| 2989 | </para> | 2989 | </para> |
| 2990 | 2990 | ||
| 2991 | <para> | 2991 | <para> |
| 2992 | Consider an example that configures the <filename>linux-yocto-3.4</filename> | 2992 | Consider an example that configures the <filename>linux-yocto-3.14</filename> |
| 2993 | kernel. | 2993 | kernel. |
| 2994 | The OpenEmbedded build system recognizes this kernel as | 2994 | The OpenEmbedded build system recognizes this kernel as |
| 2995 | <filename>linux-yocto</filename>. | 2995 | <filename>linux-yocto</filename>. |
| @@ -3023,18 +3023,18 @@ | |||
| 3023 | The actual <filename>.config</filename> is located in the area where the | 3023 | The actual <filename>.config</filename> is located in the area where the |
| 3024 | specific kernel is built. | 3024 | specific kernel is built. |
| 3025 | For example, if you were building a Linux Yocto kernel based on the | 3025 | For example, if you were building a Linux Yocto kernel based on the |
| 3026 | Linux 3.4 kernel and you were building a QEMU image targeted for | 3026 | Linux 3.14 kernel and you were building a QEMU image targeted for |
| 3027 | <filename>x86</filename> architecture, the | 3027 | <filename>x86</filename> architecture, the |
| 3028 | <filename>.config</filename> file would be located here: | 3028 | <filename>.config</filename> file would be located here: |
| 3029 | <literallayout class='monospaced'> | 3029 | <literallayout class='monospaced'> |
| 3030 | poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f... | 3030 | poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.14.11+git1+84f... |
| 3031 | ...656ed30-r1/linux-qemux86-standard-build | 3031 | ...656ed30-r1/linux-qemux86-standard-build |
| 3032 | </literallayout> | 3032 | </literallayout> |
| 3033 | <note> | 3033 | <note> |
| 3034 | The previous example directory is artificially split and many of the characters | 3034 | The previous example directory is artificially split and many of the characters |
| 3035 | in the actual filename are omitted in order to make it more readable. | 3035 | in the actual filename are omitted in order to make it more readable. |
| 3036 | Also, depending on the kernel you are using, the exact pathname | 3036 | Also, depending on the kernel you are using, the exact pathname |
| 3037 | for <filename>linux-yocto-3.4...</filename> might differ. | 3037 | for <filename>linux-yocto-3.14...</filename> might differ. |
| 3038 | </note> | 3038 | </note> |
| 3039 | </para> | 3039 | </para> |
| 3040 | 3040 | ||
| @@ -3227,7 +3227,9 @@ | |||
| 3227 | 3227 | ||
| 3228 | <para> | 3228 | <para> |
| 3229 | The example assumes a clean build exists for the <filename>qemux86</filename> | 3229 | The example assumes a clean build exists for the <filename>qemux86</filename> |
| 3230 | machine in a Source Directory named <filename>poky</filename>. | 3230 | machine in a |
| 3231 | <link linkend='source-directory'>Source Directory</link> | ||
| 3232 | named <filename>poky</filename>. | ||
| 3231 | Furthermore, the <link linkend='build-directory'>Build Directory</link> is | 3233 | Furthermore, the <link linkend='build-directory'>Build Directory</link> is |
| 3232 | <filename>build</filename> and is located in <filename>poky</filename> and | 3234 | <filename>build</filename> and is located in <filename>poky</filename> and |
| 3233 | the kernel is based on the Linux 3.4 kernel. | 3235 | the kernel is based on the Linux 3.4 kernel. |
| @@ -3246,7 +3248,20 @@ | |||
| 3246 | <title>Create a Layer for your Changes</title> | 3248 | <title>Create a Layer for your Changes</title> |
| 3247 | 3249 | ||
| 3248 | <para> | 3250 | <para> |
| 3249 | The first step is to create a layer so you can isolate your changes: | 3251 | The first step is to create a layer so you can isolate your |
| 3252 | changes. | ||
| 3253 | Rather than use the <filename>yocto-layer</filename> script | ||
| 3254 | to create the layer, this example steps through the process | ||
| 3255 | by hand. | ||
| 3256 | If you want information on the script that creates a general | ||
| 3257 | layer, see the | ||
| 3258 | "<link linkend='creating-a-general-layer-using-the-yocto-layer-script'>Creating a General Layer Using the yocto-layer Script</link>" | ||
| 3259 | section. | ||
| 3260 | </para> | ||
| 3261 | |||
| 3262 | <para> | ||
| 3263 | These two commands create a directory you can use for your | ||
| 3264 | layer: | ||
| 3250 | <literallayout class='monospaced'> | 3265 | <literallayout class='monospaced'> |
| 3251 | $ cd ~/poky | 3266 | $ cd ~/poky |
| 3252 | $ mkdir meta-mylayer | 3267 | $ mkdir meta-mylayer |
