Re: [yocto] Managing multiple builds

2019-02-15 Thread Mike Looijmans
The first thing you should realize is that providing your recipe files will produce a lot more insight into your issue than lengthy e-mails ever will. What I was attempting to convey to you is that you should move your "distro" parameters into the "machine" config. Then just build for multiple m

Re: [yocto] Managing multiple builds

2019-02-14 Thread Timothy Froehlich
Thank you, that looks like a very good idea. On Thu, Feb 14, 2019 at 8:28 AM Ulf Samuelsson wrote: > Den 2019-02-14 kl. 10:00, skrev Alexander Kanavin: > > On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich > wrote: > >> Hi, I've been struggling a bit with this question. I want to use Yocto > to b

Re: [yocto] Managing multiple builds

2019-02-14 Thread Timothy Froehlich
I'm considering that. It's the kernel build (cmdline) and the image build (RaspberryPi, the config.txt) recipes from the meta-raspberrypi layer. Setting it in a distro.conf, gated behind a "DEVBUILD=1/0" flag should work, I think. Also, please see my response to Mike Looijmans's reply. On Thu, Fe

Re: [yocto] Managing multiple builds

2019-02-14 Thread Timothy Froehlich
It'll be multiple software loads (with different required kernel modules and things like) over at least two machines. These products will do very different things but I want to use the same base and take advantage of OE's sstate, etc. So I want to be clear, I can figure out how to piece things tog

Re: [yocto] Managing multiple builds

2019-02-14 Thread Ulf Samuelsson
Den 2019-02-14 kl. 10:00, skrev Alexander Kanavin: On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich wrote: Hi, I've been struggling a bit with this question. I want to use Yocto to build two+ products with separate dev/prod images for each (dev including debug-tweaks, etc.). I've ruled out sep

Re: [yocto] Managing multiple builds

2019-02-14 Thread Mike Looijmans
Two products sounds like two machines. Just create a machine.conf for each product (even if they use similar hardware), then you don't need overrides elsewhere. OE/Yocto is smart enough to figure out what needs to be (re)built. Some OE projects build the same image(s) for over 40 machines (and

Re: [yocto] Managing multiple builds

2019-02-14 Thread Alexander Kanavin
On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich wrote: > Hi, I've been struggling a bit with this question. I want to use Yocto to > build two+ products with separate dev/prod images for each (dev including > debug-tweaks, etc.). I've ruled out separate image recipes because my dev > builds nee

[yocto] Managing multiple builds

2019-02-13 Thread Timothy Froehlich
Hi, I've been struggling a bit with this question. I want to use Yocto to build two+ products with separate dev/prod images for each (dev including debug-tweaks, etc.). I've ruled out separate image recipes because my dev builds need ENABLE_UART on my RaspberryPi and that needs to be set at the con