* slightly confused about .bbappend file and FILESPATH
@ 2012-12-06 18:03 Robert P. J. Day
2012-12-06 18:13 ` Mark Hatle
0 siblings, 1 reply; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-06 18:03 UTC (permalink / raw)
To: OE Core mailing list
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.
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))}"
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
so my *understanding* is that this should result in nothing more
than the "interfaces" file from the original oe-core recipe being
overridden, based on the enhanced entries at the front of FILESPATH
that should search in the meta-ti layer first.
but here's the problem -- for fun, i used chris larson's bitbake-env
to print the value of FILESPATH for that recipe when building for
beagle, and formatted to get:
FILESPATH="/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/linux-gnueabi
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/arm
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/build-linux
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/pn-netbase
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/beagleboard
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/omap3
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/class-target
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/forcevariable
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/libc-glibc
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/beagleboard
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/omap3
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/beagleboard
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/omap3
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/beagleboard
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/omap3
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/"
see the oddity? the first few entries will *not* find the
interfaces file in the meta-ti layer, as they don't refer to the
"netbase-5.0" directory (as do the ones in oe-core).
am i just not understanding something basic here? i'm building a
core-image-minimal for a beagle right now to see what i end up with,
but given the FILESPATH above, how is the build supposed to pick up
the beagle-specific "intxgerfaces" file without a reference to that
meta-ti directory "netbase-5.0"?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
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
0 siblings, 1 reply; 8+ messages in thread
From: Mark Hatle @ 2012-12-06 18:13 UTC (permalink / raw)
To: openembedded-core
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}
--Mark
>
> so my *understanding* is that this should result in nothing more
> than the "interfaces" file from the original oe-core recipe being
> overridden, based on the enhanced entries at the front of FILESPATH
> that should search in the meta-ti layer first.
>
> but here's the problem -- for fun, i used chris larson's bitbake-env
> to print the value of FILESPATH for that recipe when building for
> beagle, and formatted to get:
>
> FILESPATH="/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/linux-gnueabi
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/arm
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/build-linux
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/pn-netbase
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/beagleboard
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/omap3
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/class-target
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/forcevariable
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/libc-glibc
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/beagleboard
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/omap3
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/beagleboard
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/omap3
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/beagleboard
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/omap3
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/"
>
> see the oddity? the first few entries will *not* find the
> interfaces file in the meta-ti layer, as they don't refer to the
> "netbase-5.0" directory (as do the ones in oe-core).
>
> am i just not understanding something basic here? i'm building a
> core-image-minimal for a beagle right now to see what i end up with,
> but given the FILESPATH above, how is the build supposed to pick up
> the beagle-specific "intxgerfaces" file without a reference to that
> meta-ti directory "netbase-5.0"?
>
> rday
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
2012-12-06 18:13 ` Mark Hatle
@ 2012-12-06 18:19 ` Robert P. J. Day
2012-12-10 23:03 ` Martin Jansa
0 siblings, 1 reply; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-06 18:19 UTC (permalink / raw)
To: Mark Hatle; +Cc: openembedded-core
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.
thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
2012-12-06 18:19 ` Robert P. J. Day
@ 2012-12-10 23:03 ` Martin Jansa
2012-12-11 12:54 ` Robert P. J. Day
2012-12-11 19:39 ` Robert P. J. Day
0 siblings, 2 replies; 8+ messages in thread
From: Martin Jansa @ 2012-12-10 23:03 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: openembedded-core
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
2012-12-10 23:03 ` Martin Jansa
@ 2012-12-11 12:54 ` Robert P. J. Day
2012-12-11 19:39 ` Robert P. J. Day
1 sibling, 0 replies; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-11 12:54 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Tue, 11 Dec 2012, Martin Jansa wrote:
> 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):
i'm not sure what i'm supposed to be seeing in the above. are you
saying that the above will automatically handle the example i posted
above?
i configured the meta-ti layer and used chris larson's bitbake-env
utility (which should really be added as an official tool to bitbake
given its awesome awesomeness) and examined FILESPATH for the netbase
recipe:
$ bitbake-env -r netbase FILESPATH | tr : '\n'
Parsing recipes..done.
# FILESPATH="${@base_set_filespath(["${THISDIR}/${PN}"], d)}
${@base_set_filespath(["${FILE_DIRNAME}/${BP}",
"${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
FILESPATH="/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/linux-gnueabi
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/arm
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/build-linux
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/pn-netbase
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/dm814x-evm
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/ti814x
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/class-target
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/forcevariable
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/libc-glibc
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
... snip ...
as you can see, all of the checking done in the meta-ti layer
represents the netbase/netbase directory, which won't help since, in
meta-ti, it's actually netbase/netbase-5.0/. i built a dm8148 image
using meta-ti and, sure enough, the network interfaces file that
should have come from meta-ti came instead from oe-core for what i
concluded was a fairly obvious reason.
or am i misundertanding something? wouldn't be the first time...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
2012-12-10 23:03 ` Martin Jansa
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
1 sibling, 1 reply; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-11 19:39 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Tue, 11 Dec 2012, Martin Jansa wrote:
> 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):
i'm still not sure what your point is here. to be perfectly clear,
if i'm pulling in the meta-ti layer and building a core-image-minimal
for a beagleboard, it appears that the overriding network interfaces
file from the meta-ti layer does *not* override the one from oe-core
since this is the full value of FILESPATH being used:
# FILESPATH="${@base_set_filespath(["${THISDIR}/${PN}"], d)}
${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
FILESPATH="/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/linux-gnueabi
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/arm
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/build-linux
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/pn-netbase
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/dm814x-evm
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/ti814x
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/class-target
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/forcevariable
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/libc-glibc
/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/dm814x-evm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ti814x
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/dm814x-evm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ti814x
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/linux-gnueabi
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/arm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/build-linux
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/pn-netbase
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/dm814x-evm
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/ti814x
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/class-target
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/forcevariable
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/libc-glibc
/home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/"
note that the directories from the meta-ti layer don't include the
(correct) value of netbase/netbase-5.0, since (as i understand it) the
line in base.bbclass you refer to:
FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", \
"${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
only causes the expansion into the common variants of the directory
name for the oe-core layer (as you can see above). so under oe-core,
you'll get the automatic directory name variants netbase, netbase-5.0
and files (exactly what you see above).
but under the meta-ti layer for netbase, you *don't* get that since
here's the netbase_5.0.bbappend file:
THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
which (unless i'm cripplingly mistaken) will prepend the set of
directories *only* under precisely that name "${THISDIR}/${PN}", which
is exactly netbase/netbase, which is wrong.
am i completely misunderstanding what's happening here? as i see
it, the trivial fix is to simply tweak the .bbappend file to read:
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}}"], d)}:"
i already submitted a patch for that to the meta-ti list, i just want
to confirm that the above really is a bug in the netbase .bbappend
file in that it won't pick up the overriding interfaces file.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
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
0 siblings, 1 reply; 8+ messages in thread
From: Martin Jansa @ 2012-12-12 4:57 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 8851 bytes --]
On Tue, Dec 11, 2012 at 02:39:16PM -0500, Robert P. J. Day wrote:
> On Tue, 11 Dec 2012, Martin Jansa wrote:
>
> > 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):
>
> i'm still not sure what your point is here.
That all you need is 1 line:
FILESEXTRAPATHS_prepend := "${THISDIR}/${BP}:"
> to be perfectly clear,
> if i'm pulling in the meta-ti layer and building a core-image-minimal
> for a beagleboard, it appears that the overriding network interfaces
> file from the meta-ti layer does *not* override the one from oe-core
> since this is the full value of FILESPATH being used:
>
> # FILESPATH="${@base_set_filespath(["${THISDIR}/${PN}"], d)}
> ${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
> FILESPATH="/home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/linux-gnueabi
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/arm
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/build-linux
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/pn-netbase
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/dm814x-evm
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/ti814x
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/class-target
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/forcevariable
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/libc-glibc
> /home/rpjday/OE/dist/layers/meta-ti/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/dm814x-evm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ti814x
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/dm814x-evm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ti814x
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/dm814x-evm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/ti814x
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/class-target
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/forcevariable
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/libc-glibc
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/files/"
>
> note that the directories from the meta-ti layer don't include the
> (correct) value of netbase/netbase-5.0, since (as i understand it) the
> line in base.bbclass you refer to:
>
> FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", \
> "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
>
> only causes the expansion into the common variants of the directory
> name for the oe-core layer (as you can see above). so under oe-core,
> you'll get the automatic directory name variants netbase, netbase-5.0
> and files (exactly what you see above).
>
> but under the meta-ti layer for netbase, you *don't* get that since
> here's the netbase_5.0.bbappend file:
>
> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
> FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
>
> which (unless i'm cripplingly mistaken) will prepend the set of
> directories *only* under precisely that name "${THISDIR}/${PN}", which
> is exactly netbase/netbase, which is wrong.
>
> am i completely misunderstanding what's happening here? as i see
> it, the trivial fix is to simply tweak the .bbappend file to read:
>
> FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}}"], d)}:"
>
> i already submitted a patch for that to the meta-ti list, i just want
> to confirm that the above really is a bug in the netbase .bbappend
> file in that it won't pick up the overriding interfaces file.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: slightly confused about .bbappend file and FILESPATH
2012-12-12 4:57 ` Martin Jansa
@ 2012-12-12 11:35 ` Robert P. J. Day
0 siblings, 0 replies; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-12 11:35 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Wed, 12 Dec 2012, Martin Jansa wrote:
> On Tue, Dec 11, 2012 at 02:39:16PM -0500, Robert P. J. Day wrote:
> > On Tue, 11 Dec 2012, Martin Jansa wrote:
> >
> > > 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):
> >
> > i'm still not sure what your point is here.
>
> That all you need is 1 line:
> FILESEXTRAPATHS_prepend := "${THISDIR}/${BP}:"
right, i believe that was the point i was circling around all this
time. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-12-12 11:49 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox