When building in a non CI env this all is not
needed as the user might accidentally end up losing all the build
artifacts that are not intendeed to. On CI systems its better to delete
it via extra step outside setup
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-multimedia depends on meta-python. I'm not sure why it's
necessary to add all the dependent layers in order, but if I don't do
this I get a bunch of exceptions during setup.sh that result in no
meta-python in my bblayers.conf and thus a non-functional bitbake.
setup.sh was already explicitly adding meta-python, so this patch just
adds it before meta-multimedia. That fixes the errors on my side.
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Minor fix.
Changed to be buildable according to input of each MACHINE.
Add buildable machine's information in script.
Signed-off-by: sungwon.pino <sungwon.pino@gmail.com>
These policies enabled essential features like package management
and ssh server in images, additionally remove static libs and use
uninative
Signed-off-by: Khem Raj <raj.khem@gmail.com>
We document using oe-core and bitbake but the environment was setting
for poky, this fixes that, plus riscv64 is not enabled as default tatget
in poky where as it is in oe-core
Signed-off-by: Khem Raj <raj.khem@gmail.com>
