Can't share build trees?
I have a system which has both PowerPC and ARM/OMAP components. They share a common Poky/Yocto layer, so I thought I'd be able to also share a build tree. So, I tried something like this:
% . /opt/poky/oe-init-build-env my_target
% MACHINE=MY_OMAP bitbake omap-image
% MACHINE=MY_PPC bitbake ppc-image
All seemed fine the first time through. The images were built as expected and worked well.
Sadly, when I tried to build something else, e.g.
% MACHINE=MY_OMAP bitbake some-package
it set off rebuilding the entire cross tool chain :-(
Should this work? or should I just be aware it does not (and mostly tell my customers not to expect it to work)?
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 10 lines · Gary Thomas
I have a system which has both PowerPC and ARM/OMAP components. They share a common Poky/Yocto layer, so I thought I'd be able to also share a build tree. So, I tried something like this:
% ./opt/poky/oe-init-build-envmy_target
% MACHINE=MY_OMAP bitbake omap-image
% MACHINE=MY_PPC bitbake ppc-imageAll seemed fine the first time through. The images were built as expected and worked well.
Quoted 6 lines
Sadly, when I tried to build something else, e.g.
% MACHINE=MY_OMAP bitbake some-package
it set off rebuilding the entire cross tool chain :-(Should this work? or should I just be aware it does not (and mostly tell my customers not to expect it to work)?
It should work and its the way I use Poky. Did you update the metadata between these builds changing the toolchain version for example (e.g. gcc 4.6.0 testing)?
Cheers,
Richard
Quoted 15 lines · Richard Purdie
Quoted 14 lines · Gary Thomas
I have a system which has both PowerPC and ARM/OMAP components. They share a common Poky/Yocto layer, so I thought I'd be able to also share a build tree. So, I tried something like this:
% ./opt/poky/oe-init-build-envmy_target
% MACHINE=MY_OMAP bitbake omap-image
% MACHINE=MY_PPC bitbake ppc-imageAll seemed fine the first time through. The images were built as expected and worked well.
Sadly, when I tried to build something else, e.g.
% MACHINE=MY_OMAP bitbake some-package
it set off rebuilding the entire cross tool chain :-(
Quoted 6 lines
Quoted 2 lines
Should this work? or should I just be aware it does not (and mostly tell my customers not to expect it to work)?
It should work and its the way I use Poky. Did you update the metadata between these builds changing the toolchain version for example (e.g. gcc 4.6.0 testing)?
No changes, just changed the MACHINE
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 16 lines · Gary Thomas
Quoted 15 lines · Richard Purdie
Quoted 14 lines · Gary Thomas
I have a system which has both PowerPC and ARM/OMAP components. They share a common Poky/Yocto layer, so I thought I'd be able to also share a build tree. So, I tried something like this:
% ./opt/poky/oe-init-build-envmy_target
% MACHINE=MY_OMAP bitbake omap-image
% MACHINE=MY_PPC bitbake ppc-imageAll seemed fine the first time through. The images were built as expected and worked well.
Sadly, when I tried to build something else, e.g. % MACHINE=MY_OMAP bitbake some-package
it set off rebuilding the entire cross tool chain :-(
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Should this work? or should I just be aware it does not (and mostly tell my customers not to expect it to work)?
It should work and its the way I use Poky. Did you update the metadata between these builds changing the toolchain version for example (e.g. gcc 4.6.0 testing)?
No changes, just changed the MACHINE
I'll try it again, just to make sure I can duplicate it.
I'm happy to hear that this should work.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------