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 counting)...

On 14-02-19 01:34, 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 need ENABLE_UART on my RaspberryPi and that needs to be set at the 
> conf 
> level (I've got it set conditionally in my base dist conf). Multiconfig 
> looked 
> promising, but I'm not happy about how long the parsing takes to start a 
> build. "--postread" looked nice, but I've barely seen it mentioned so I'm 
> worried that it's not well supported.
> 
> Basically, what do most people do for controlling their builds?
> Tim Froehlich
> Embedded Linux Engineer
> tfroehl...@archsys.io <mailto:tfroehl...@archsys.io>
> 215-218-8955
> 

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to