I had no problem building with this configuration (up to date master): Build Configuration: BB_VERSION = "1.34.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-my-distro-l

What are you expecting to happen? 'devshell' is just that - a shell environment (e.g. bash) where you are set up to "develop" (tinker, explore, etc) the given recipe.

Such as?

OK, thanks. Any recommendations for an alternative, other than 'xterm' (whose "main.c" has said "Warning! there be dragons here!" for more than 20 years :-)

I'm impressed! That eliminated all of them :-) What would I lose by do this, in general, as it's pretty obvious that python3 is not needed by any of the recipes I use?

Not that: I filtered out all uses of python3-native - these are only *target* dependencies None of my recipes build -ptest stuff: $ find tmp/deploy/ipk/ -name "*ptest*"

I'm building using Poky/Yocto master 576821ea0a7558b626ccc87e9ae0e9ee40864956 and I've noticed that python3 (target) is being built for my image, but it doesn't end up in the actual image. None of my

# opkg --version opkg version 0.3.4 (libsolv 0.6.27) Built using poky:master (a3d160f9e5826140cc8d6b2ed1b38bf022443b08) Attached. This looks like good information - opkd thinks that eudev-hwdb is in a

How does one change the terminal font (size) used by matchbox-terminal in the sato desktop? I tried the 'matchbox-appearance' app and it didn't have any affect, nor could I see a way to change the fon

Very interesting - I'm building two different system images for this target and I tried to apply the BAD_RECOMMENDS to only one of them. The target images (pure result of bitbake) did the right thing,

Thanks for the suggestion. Sadly, still no go.

In my local.conf, I have this (to save space in my embedded image): BAD_RECOMMENDATIONS = "udev-rules-imx eudev-hwdb" Is there a different way I can trim these packages, e.g. leave them in for some im

I didn't see much more info here: $ bitbake-diffsigs -d -t gcc-cross-arm compile NOTE: Started PRServer with DBfile: /build/p0382_2016-01-13/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 40390, PID: 1004

Happy to give it a go, just let me know what you need Thanks

Would you mind sharing your configuration (conf/local.conf, conf/bblayers.conf)? I'm mostly interested in trying this on my RaspberryPi3. Thanks

I just updated my Poky/Yocto master (a3d160f9e5826140cc8d6b2ed1b38bf022443b08) and it happened again. I'm still interested in why gcc-cross-arm had to be rebuilt _again_, so I ran: $ bitbake-diffsigs

You were correct, using MACHINE_EXTRA_RRECOMMENDS didn't work, but explicitly including cups-lib did. Not very intuitive :-(

Not part of the default Yocto setup, but what you are asking for seems to be a perfect fit for the [Android/Google] repo tool.

I see that the latest master update has brought a progress bar for this (and presumably other 'cmake' based packages) - very nice :-) Now [tongue-in-cheek], can someone do something about the horrendo

No, it's in <layer>/conf/layer.conf for the <layer> in question.