diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-05-26 14:17:20 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-07-28 18:02:30 +0100 |
| commit | 5644756bc7abe3e4bc82ba28af1bce58bfd2f2ad (patch) | |
| tree | d8e12eb7397b74725a1aa42824a7c0e07bdce778 /documentation/kernel-dev | |
| parent | 4764062664e1d4c2d484872f562c4050b413ff4e (diff) | |
| download | poky-5644756bc7abe3e4bc82ba28af1bce58bfd2f2ad.tar.gz | |
kernel-dev: Added new requirement for working with yocto-linux-custom.bb
Fixes [YOCTO #6611]
Added a new step to the "Working With Your Own Sources" section
so that the user is aware of needing to provide a defconfig file
or configuration fragments to the SRC_URI variable when working
with the yocto-linux-custom.bb recipe.
(From yocto-docs rev: dd25274979f689ae9135158279080add19a98393)
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')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 26 |
1 files changed, 23 insertions, 3 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 618d60cbaf..e5e26bc513 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml | |||
| @@ -631,15 +631,35 @@ | |||
| 631 | to store your patches and configuration files (e.g. | 631 | to store your patches and configuration files (e.g. |
| 632 | <filename>linux-yocto-myproject</filename>). | 632 | <filename>linux-yocto-myproject</filename>). |
| 633 | </para></listitem> | 633 | </para></listitem> |
| 634 | <listitem><para>Make sure you have either a | ||
| 635 | <filename>defconfig</filename> file or configuration | ||
| 636 | fragment files. | ||
| 637 | When you use the <filename>linux-yocto-custom.bb</filename> | ||
| 638 | recipe, you must specify a configuration. | ||
| 639 | If you do not have a <filename>defconfig</filename> file, | ||
| 640 | you can run the following: | ||
| 641 | <literallayout class='monospaced'> | ||
| 642 | $ make defconfig | ||
| 643 | </literallayout> | ||
| 644 | After running the command, copy the resulting | ||
| 645 | <filename>.config</filename> to the | ||
| 646 | <filename>files</filename> directory as "defconfig" and | ||
| 647 | then add it to the | ||
| 648 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink> | ||
| 649 | variable in the recipe. | ||
| 650 | </para></listitem> | ||
| 634 | <listitem><para>Edit the following variables in your recipe | 651 | <listitem><para>Edit the following variables in your recipe |
| 635 | as appropriate for your project: | 652 | as appropriate for your project: |
| 636 | <itemizedlist> | 653 | <itemizedlist> |
| 637 | <listitem><para><ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>: | 654 | <listitem><para><ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>: |
| 638 | The <filename>SRC_URI</filename> should be a Git | 655 | The <filename>SRC_URI</filename> should specify |
| 639 | repository that uses one of the supported Git fetcher | 656 | a Git repository that uses one of the supported Git |
| 640 | protocols (i.e. <filename>file</filename>, | 657 | fetcher protocols (i.e. <filename>file</filename>, |
| 641 | <filename>git</filename>, <filename>http</filename>, | 658 | <filename>git</filename>, <filename>http</filename>, |
| 642 | and so forth). | 659 | and so forth). |
| 660 | The <filename>SRC_URI</filename> variable should | ||
| 661 | also specify either a <filename>defconfig</filename> | ||
| 662 | file or some configuration fragment files. | ||
| 643 | The skeleton recipe provides an example | 663 | The skeleton recipe provides an example |
| 644 | <filename>SRC_URI</filename> as a syntax reference. | 664 | <filename>SRC_URI</filename> as a syntax reference. |
| 645 | </para></listitem> | 665 | </para></listitem> |
