On 8 October 2017 at 18:04, Eric Schwarz <e...@sw-optimization.com> wrote:
> 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. Well it's ugly, so if you want a patch in oe-core then don't introduce ugly for your convenience. > 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? > You need to inherit python3native, as python (and some others) are opt-in. > 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. > Yes, bb.utils.filter() is a new function that isn't in morty. Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto