summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-06-01 08:31:54 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-10-21 23:11:38 +0100
commit8124686aa2175da8f18d41403c9305fe3e2d0806 (patch)
tree31feafa2f224ef55f6b2fc2f823e901f75830772
parent8a19731e4df8537a6628b74c1f7041b7a6aeeb17 (diff)
downloadast2050-yocto-poky-8124686aa2175da8f18d41403c9305fe3e2d0806.zip
ast2050-yocto-poky-8124686aa2175da8f18d41403c9305fe3e2d0806.tar.gz
kernel-dev: Added kernel-devsrc information for building on target
I added a clarifying paragraph at the start of the section that talks about building on the target hardware. Included kernel-devsrc and rationale for why a user would even do this (it is not normal). (From yocto-docs rev: 95ae213b80cb45b5e9b7b161b2968dca6315e1da) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml20
1 files changed, 18 insertions, 2 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index e5e26bc..532e2e8 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -736,12 +736,26 @@
<title>Building Out-of-Tree Modules on the Target</title>
<para>
+ While the traditional Yocto Project development model would be
+ to include kernel modules as part of the normal build
+ process, you might find it useful to build modules on the
+ target.
+ This could be the case if your target system is capable
+ and powerful enough to handle the necessary compilation.
+ Before deciding to build on your target, however, you should
+ consider the benefits of using a proper cross-development
+ environment from your build host.
+ </para>
+
+ <para>
If you want to be able to build out-of-tree modules on
the target, there are some steps you need to take
on the target that is running your SDK image.
Briefly, the <filename>kernel-dev</filename> package
is installed by default on all
- <filename>*.sdk</filename> images.
+ <filename>*.sdk</filename> images and the
+ <filename>kernel-devsrc</filename> package is installed
+ on many of the <filename>*.sdk</filename> images.
However, you need to create some scripts prior to
attempting to build the out-of-tree modules on the target
that is running that image.
@@ -759,7 +773,9 @@
Because all SDK image recipes include
<filename>dev-pkgs</filename>, the
<filename>kernel-dev</filename> packages will be installed
- as part of the SDK image.
+ as part of the SDK image and the
+ <filename>kernel-devsrc</filename> packages will be installed
+ as part of applicable SDK images.
The SDK uses the scripts when building out-of-tree
modules.
Once you have switched to that directory and created the
OpenPOWER on IntegriCloud