From: Darren Hart <dvhart@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: kernel manual: confusing coverage of FILESEXTRAPATHS_prepend
Date: Wed, 25 Feb 2015 09:08:47 -0800 [thread overview]
Message-ID: <D1134136.BEE7D%dvhart@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1502250351310.26693@localhost>
On 2/25/15, 12:54 AM, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>
> minor quibble about kernel dev manual -- section 2.2.1, "creating
>the append file", uses the example of:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
>while section 2.2.3 uses:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
>both sections kind of implying that that's the way to do it, without
>making it clear that *either* way works as long as the variable
>prepend matches up with the directory name.
>
> both ways are correct, of course, but the wording is a bit
>confusing.
Thanks, I agree, the same syntax should be used throughout the document.
The FILESEXTRAPATHS variable does correctly link to the ref manual where
people can get details on usage.
For simplicity, I should using "files" instead of ${PN}, it avoids the
"make sure your directory name matches ${PN}" issue.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2015-02-25 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 8:54 kernel manual: confusing coverage of FILESEXTRAPATHS_prepend Robert P. J. Day
2015-02-25 13:44 ` Joe MacDonald
2015-02-25 13:51 ` Gary Thomas
2015-02-25 15:49 ` Rifenbark, Scott M
2015-02-26 9:12 ` Robert P. J. Day
2015-02-26 9:20 ` Robert P. J. Day
2015-02-26 10:17 ` Paul Eggleton
2015-02-26 20:29 ` Robert P. J. Day
2015-02-25 17:08 ` Darren Hart [this message]
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=D1134136.BEE7D%dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--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.