All of lore.kernel.org
 help / color / mirror / Atom feed
From: jfabernathy <jfabernathy@gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Documentation improvement
Date: Fri, 06 Jul 2012 14:58:49 -0400	[thread overview]
Message-ID: <4FF73569.4000105@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]

I was looking at the Yocto Development Manual (Latest), section 
4.6.2. Creating Config Fragments.  I was confused about the file 
statement and the naming of the directory to locate the fragment file 
until I found a similar discussion in the BSP Guide (lastest) section 
1.2.10. Linux Kernel Configuration.

The section there is much more understandable.  I think we need to 
modify the development manual or have it point to the BSP manual. The 
text from there (below) I think is better.  I still think it's confusing 
about the naming of the subdirectory where the myconfig goes. Maybe a 
complete example would be good.

    For example, suppose you had a set of configuration options in a
    file called |myconfig|. If you put that file inside a directory
    named |linux-yocto| and then added a |SRC_URI| statement such as the
    following to the append file, those configuration options will be
    picked up and applied when the kernel is built.

          SRC_URI += "file://myconfig"
                     

    As mentioned earlier, you can group related configurations into
    multiple files and name them all in the |SRC_URI| statement as well.
    For example, you could group separate configurations specifically
    for Ethernet and graphics into their own files and add those by
    using a |SRC_URI| statement like the following in your append file:

          SRC_URI += "file://myconfig \
                 file://eth.cfg \
                 file://gfx.cfg"
                     


[-- Attachment #2: Type: text/html, Size: 2246 bytes --]

             reply	other threads:[~2012-07-06 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 18:58 jfabernathy [this message]
2012-07-06 21:06 ` Documentation improvement Rifenbark, Scott M
2012-07-06 21:16   ` James Abernathy
2012-07-09 12:50   ` James Abernathy
2012-08-27 16:02 ` Rifenbark, Scott M
  -- strict thread matches above, loose matches on Subject: below --
2012-01-12 21:01 documentation improvement Gergely Buday
2012-01-12 21:22 ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FF73569.4000105@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.