diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-06-01 08:31:54 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-07-28 18:02:31 +0100 |
commit | 926d70f9b90e6624578655a0af35db36203b8bdb (patch) | |
tree | 86300b806480b4ea1b777e68aebbb79f92d7d11e /documentation/kernel-dev/kernel-dev-common.xml | |
parent | 39bcabf5135d5a0ac0df289dbead2e40a104e4f1 (diff) | |
download | poky-926d70f9b90e6624578655a0af35db36203b8bdb.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: 5c42f981e9e54ae286b5ea5faf4dd29486c6350c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-common.xml')
-rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 20 |
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 e5e26bc513..532e2e87a6 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml | |||
@@ -736,12 +736,26 @@ | |||
736 | <title>Building Out-of-Tree Modules on the Target</title> | 736 | <title>Building Out-of-Tree Modules on the Target</title> |
737 | 737 | ||
738 | <para> | 738 | <para> |
739 | While the traditional Yocto Project development model would be | ||
740 | to include kernel modules as part of the normal build | ||
741 | process, you might find it useful to build modules on the | ||
742 | target. | ||
743 | This could be the case if your target system is capable | ||
744 | and powerful enough to handle the necessary compilation. | ||
745 | Before deciding to build on your target, however, you should | ||
746 | consider the benefits of using a proper cross-development | ||
747 | environment from your build host. | ||
748 | </para> | ||
749 | |||
750 | <para> | ||
739 | If you want to be able to build out-of-tree modules on | 751 | If you want to be able to build out-of-tree modules on |
740 | the target, there are some steps you need to take | 752 | the target, there are some steps you need to take |
741 | on the target that is running your SDK image. | 753 | on the target that is running your SDK image. |
742 | Briefly, the <filename>kernel-dev</filename> package | 754 | Briefly, the <filename>kernel-dev</filename> package |
743 | is installed by default on all | 755 | is installed by default on all |
744 | <filename>*.sdk</filename> images. | 756 | <filename>*.sdk</filename> images and the |
757 | <filename>kernel-devsrc</filename> package is installed | ||
758 | on many of the <filename>*.sdk</filename> images. | ||
745 | However, you need to create some scripts prior to | 759 | However, you need to create some scripts prior to |
746 | attempting to build the out-of-tree modules on the target | 760 | attempting to build the out-of-tree modules on the target |
747 | that is running that image. | 761 | that is running that image. |
@@ -759,7 +773,9 @@ | |||
759 | Because all SDK image recipes include | 773 | Because all SDK image recipes include |
760 | <filename>dev-pkgs</filename>, the | 774 | <filename>dev-pkgs</filename>, the |
761 | <filename>kernel-dev</filename> packages will be installed | 775 | <filename>kernel-dev</filename> packages will be installed |
762 | as part of the SDK image. | 776 | as part of the SDK image and the |
777 | <filename>kernel-devsrc</filename> packages will be installed | ||
778 | as part of applicable SDK images. | ||
763 | The SDK uses the scripts when building out-of-tree | 779 | The SDK uses the scripts when building out-of-tree |
764 | modules. | 780 | modules. |
765 | Once you have switched to that directory and created the | 781 | Once you have switched to that directory and created the |