Hi Ross,
DEPENDS += "bc-native dtc-native"
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"
Don't _append when you can just extend the assignment above.
I just did it that way for the moment since I wanted to circumvent merge
conflicts when I upgrade the underlying recipes from openembedded.
Depending on python-native does nothing as the binary isn't in $PATH
still.
I thought any Yocto native binaries built are in the PATH automatically.
- How
to fix this/do it correctly?
Can you provide a configuration to make U-Boot build on x86 for
testing?
I put now some patches in ordered manner on top of the original recipes
from
openembedded.
However, before sending I would like to fix two issues so the recipes
can go
into mainline immediately.
1.) I am working w/ -morty Yocto branch at the moment. The 'u-boot.inc'
from
openembedded does not work w/ -morty.
I get the following error "AttributeError: module 'bb.utils' has no
attribute 'filter'". Building w/ the original -morty 'u-boot.inc'
works.
2.) There is an issue w/ the U-Boot build system that it needs the
"libgcc.a"
from the local host system [1]. I circumvented this by checking in
my
"libgcc.a" and patching the U-Boot makefile accordingly. This must
be
fixed in U-boot.
[1]... https://www.mail-archive.com/yocto@yoctoproject.org/msg36721.html
Cheers
Eric
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
