Re: [yocto] Specifying MACHINE when setting up build environment

2018-01-15 Thread Anuj Mittal
On 01/14/2018 01:07 AM, colin.helliw...@ln-systems.com wrote:
> Is there a way to specify what MACHINE is put into local.conf when first
> setting up the build directory with oe-init-build-env?
> I have my own TEMPLATECONF which I use, but I'd like to be able to set the
> MACHINE on the command line rather than having to then modify local.conf
> 
> 

You can specify a local.conf.sample and have TEMPLATECONF point to the
directory with that file in it. Please see scripts/oe-setup-builddir in
poky/meta to see how it is picked up.

Thanks,
Anuj
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Specifying MACHINE when setting up build environment

2018-01-15 Thread Colin Helliwell

> On 13 January 2018 at 18:52 Jan Siegmund wrote:
> 
> 
> Hi,
> 
> Am 13.01.2018 um 18:07 schrieb colin.helliw...@ln-systems.com:
> > Is there a way to specify what MACHINE is put into local.conf when first
> > setting up the build directory with oe-init-build-env?
> > I have my own TEMPLATECONF which I use, but I'd like to be able to set the
> > MACHINE on the command line rather than having to then modify local.conf
> If it would suit your needs to specify the MACHINE on every bitbake call,
> try
> 
> $ MACHINE= bitbake 
> 
> e. g.
> 
> $ MACHINE=qemuarm bitbake core-image-minimal
> 
> If your want to use QEMU, you can use
> 
> $ env DEPLOY_DIR_IMAGE= runqemu
> 
> Not sure if the 'env' is needed though.
> 

Thanks Jan. I don't want to have to include MACHINE on every bitbake cmd line 
though - just have it placed into the local.conf the first time the build dir 
is set up by oe-init-build-env.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Specifying MACHINE when setting up build environment

2018-01-13 Thread Jan Siegmund
Hi,

Am 13.01.2018 um 18:07 schrieb colin.helliw...@ln-systems.com:
> Is there a way to specify what MACHINE is put into local.conf when first
> setting up the build directory with oe-init-build-env?
> I have my own TEMPLATECONF which I use, but I'd like to be able to set the
> MACHINE on the command line rather than having to then modify local.conf
If it would suit your needs to specify the MACHINE on every bitbake call,
try

$ MACHINE= bitbake 

e. g.

$ MACHINE=qemuarm bitbake core-image-minimal

If your want to use QEMU, you can use

$ env DEPLOY_DIR_IMAGE= runqemu

Not sure if the 'env' is needed though.

Regards,
Jan


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


[yocto] Specifying MACHINE when setting up build environment

2018-01-13 Thread colin.helliwell
Is there a way to specify what MACHINE is put into local.conf when first
setting up the build directory with oe-init-build-env?
I have my own TEMPLATECONF which I use, but I'd like to be able to set the
MACHINE on the command line rather than having to then modify local.conf


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