From: Denys Dmytriyenko <denys@ti.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: puzzled by FILESPATH setting in tipspkernel.inc
Date: Mon, 11 Nov 2013 14:50:57 -0500 [thread overview]
Message-ID: <20131111195057.GH24766@denix.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1311101239330.2907@oneiric>
On Sun, Nov 10, 2013 at 12:47:24PM -0500, Robert P. J. Day wrote:
>
> poking around some of the kernel recipes in the meta-ti layer and
> i'm a bit baffled by the following in
> meta-ti/recipes-kernel/linux/tipspkernel.inc:
>
> # First of all, set own FILESPATH avoiding unnecessary BP and BPN, but adding
> # extra level of major version
> FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", "${FILE_DIRNAME}/${P}", "${FILE_DIRNAME}/${PN}-${PMV}", \
> "${FILE_DIRNAME}/${PN}", "${FILE_DIRNAME}/files", "${FILE_DIRNAME}" ], d)}"
>
> i understand the mechanics of how the above works, but i'm not sure
> about that very last element in array: ${FILE_DIRNAME}, all by itself.
> is that deliberate? that is, not having any extra level such as ${PF}
> or ${P} or "files"? isn't that suggesting that files can be located in
> the main directory itself? which doesn't seem to be necessary.
That used to be the case before, but had changed a year ago:
http://cgit.openembedded.org/openembedded-core/commit/?id=3efa13cd76bbd5611805021945fc9def88d9fd93
Anyway, tipspkernel.inc is a deprecated feature and its use is discouraged
now. It remains present for some old kernel recipes to work.
--
Denys
prev parent reply other threads:[~2013-11-11 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 17:47 puzzled by FILESPATH setting in tipspkernel.inc Robert P. J. Day
2013-11-11 19:50 ` Denys Dmytriyenko [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=20131111195057.GH24766@denix.org \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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.