1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00

ref-manual: Updates to "Kernel Build Changes" in the 1.8 migration section.

Updated this according to some changes Richard and Paul wanted to
see make it into the 1.8 release.

Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: f571e35169818355fea2a20715df3e8f7405134f)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2015-04-09 11:35:18 -07:00
committed by Richard Purdie
parent be46715a9d
commit 8f39398dbf
+16 -4
View File
@@ -2034,11 +2034,11 @@
Functionality replaced by <filename>gst-player</filename>. Functionality replaced by <filename>gst-player</filename>.
</para></listitem> </para></listitem>
<listitem><para><filename>gnome-desktop</filename>: <listitem><para><filename>gnome-desktop</filename>:
This recipe is now available in This recipe is now available in
<filename>meta-gnome</filename> and is no longer needed. <filename>meta-gnome</filename> and is no longer needed.
</para></listitem> </para></listitem>
<listitem><para><filename>gsettings-desktop-schemas</filename>: <listitem><para><filename>gsettings-desktop-schemas</filename>:
This recipe is now available in This recipe is now available in
<filename>meta-gnome</filename> and is no longer needed. <filename>meta-gnome</filename> and is no longer needed.
</para></listitem> </para></listitem>
<listitem><para><filename>python-argparse</filename>: <listitem><para><filename>python-argparse</filename>:
@@ -2117,12 +2117,24 @@
In theory, migration paths have been provided for most common In theory, migration paths have been provided for most common
usages in kernel recipes but this might not work in all cases. usages in kernel recipes but this might not work in all cases.
In particular, users need to ensure that In particular, users need to ensure that
<filename>${S}</filename> (source files) and <filename>${S}</filename> (source files) and
<filename>${B}</filename> (build artifacts) are used <filename>${B}</filename> (build artifacts) are used
correctly in functions such as correctly in functions such as
<link linkend='ref-tasks-configure'><filename>do_configure</filename></link>
and
<link linkend='ref-tasks-install'><filename>do_install</filename></link>. <link linkend='ref-tasks-install'><filename>do_install</filename></link>.
For kernel recipes that do not inherit from
<filename>kernel-yocto</filename> or include
<filename>linux-yocto.inc</filename>, you might wish to
refer to the <filename>linux.inc</filename> file in the
<filename>meta-oe</filename> layer for the kinds of changes you
need to make.
For reference, here is the
<ulink url='http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-kernel/linux/linux.inc?id=fc7132ede27ac67669448d3d2845ce7d46c6a1ee'>commit</ulink>
where the <filename>linux.inc</filename> file in
<filename>meta-oe</filename> was updated.
</para> </para>
<para> <para>
Recipes that rely on the kernel source code and do not inherit Recipes that rely on the kernel source code and do not inherit
the module classes might need to add explicit dependencies on the module classes might need to add explicit dependencies on