Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: slightly confused about .bbappend file and FILESPATH
Date: Tue, 11 Dec 2012 00:03:53 +0100	[thread overview]
Message-ID: <20121210230353.GA11623@jama.jama.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1212061316510.16942@oneiric>

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

On Thu, Dec 06, 2012 at 01:19:57PM -0500, Robert P. J. Day wrote:
> On Thu, 6 Dec 2012, Mark Hatle wrote:
> 
> > On 12/6/12 12:03 PM, Robert P. J. Day wrote:
> > >
> > >    currently writing a tutorial page on how .bbappend files and
> > > FILESPATH work, and i wanted to use a live example, but now i'm
> > > confused.
> >
> > The way it works is the same way as PATH in the shell.  It's just a set of
> > search paths.
> >
> > >    using meta-ti layer, i chose to build core-image-minimal for a
> > > beagleboard, for which the meta-ti layer has the following under
> > > recipes-core/netbase/ that i want to use as an example:
> > >
> > > $ find
> > > .
> > > ./netbase_5.0.bbappend
> > > ./netbase-5.0
> > > ./netbase-5.0/beagleboard
> > > ./netbase-5.0/beagleboard/interfaces
> > > $
> > >
> > > where the .bbappend file contains only:
> > >
> > > THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
> >
> > I believe this is the default value of 'THISDIR' already, so there is no
> > reason to specify it in the .bbappend itself.
> >
> > > FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
> >
> > In this example, it's incorrect.  As you have a directory named
> > "netbase-5.0", so your FILESPATH should be: ${THISDIR}/${PN}-${PV}
> 
>   ok, so that's just a bug in the setting of FILESPATH in that one
> example?  whew.  i was seriously wondering how badly i misunderstood
> how this feature worked.
> 
>   as soon as my beagle core-image-minimal finishes building, i should
> be able to trivially check that the interfaces file used to populate
> the rootfs image is the one from oe-core and not the one that should
> have come from meta-ti.

See FILESEXTRAPATHS in other bbappends and

meta/classes/base.bbclass:FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}","${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"

+ definition of fce base_set_filespath:
meta/classes/utils.bbclass:def base_set_filespath(path, d):

Cheers,

> 
>   thanks.
> 
> rday
> 
> -- 
> 
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-12-10 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 18:03 slightly confused about .bbappend file and FILESPATH Robert P. J. Day
2012-12-06 18:13 ` Mark Hatle
2012-12-06 18:19   ` Robert P. J. Day
2012-12-10 23:03     ` Martin Jansa [this message]
2012-12-11 12:54       ` Robert P. J. Day
2012-12-11 19:39       ` Robert P. J. Day
2012-12-12  4:57         ` Martin Jansa
2012-12-12 11:35           ` Robert P. J. Day

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=20121210230353.GA11623@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox