Just a quick note that you *can* script config file alterations without
having to alter files that may be under source control, that's what
auto.conf is for :)
On Thu, Mar 25, 2021 at 7:51 AM Robert P. J. Day
wrote:
> On Thu, 25 Mar 2021, Mike Looijmans wrote:
>
> > I for one use a whitelist
On Thu, 25 Mar 2021, Mike Looijmans wrote:
> I for one use a whitelist env vars daily, both hobby and work.
>
> We tend to build for multiple machines, so in general we'd have
> something like this running on the build server:
>
> for machine in mach1 mach2 mach3 mach4 ... mach40
> do
>
I for one use a whitelist env vars daily, both hobby and work.
We tend to build for multiple machines, so in general we'd have something like
this running on the build server:
for machine in mach1 mach2 mach3 mach4 ... mach40
do
MACHINE=$machine bitbake image1 image2 image3
done
Being
On 3/25/21 9:08 AM, Robert P. J. Day wrote:
>
> kind of a philosophical question, but i'm having a discussion with
> some new colleagues about how to customize an OE (actually, wind river
> linux) build, and these colleagues have, until now, used (whitelisted)
> environment variables to pass
kind of a philosophical question, but i'm having a discussion with
some new colleagues about how to customize an OE (actually, wind river
linux) build, and these colleagues have, until now, used (whitelisted)
environment variables to pass info to the build, that info being used
to specify
