On Mon, Mar 25, 2013 at 2:45 PM, Flanagan, Elizabeth < elizabeth.flana...@intel.com> wrote:
> On Thu, Mar 21, 2013 at 8:31 AM, Trevor Woerner <twoer...@gmail.com> > wrote: > > I have looked at the output from a couple builds (nightly-fsl-arm, > > nightly-fsl-ppc, nightly-mips) and had a couple questions. > > > > Running "poky/oe-init-build-env" will produce a > > "build/conf/local.conf", but the nightly builder prefers to puts its > > configurations into "build/conf/auto.conf". Obviously there's nothing > > wrong with this, but I'm wondering why use auto.conf instead of > > local.conf? I'm guessing there's some nugget of information in this > > choice that I'm hoping to discover. > > It's nothing particularly special, except I do it to differentiate an > autogenerated local.conf from the local.conf that is created by > oe-init-build-env. I'm sure there was a different reason for it, but > the commit log never made it over from the o-hand.org svn server so... Yeah, that's basically why auto.conf is supported at all. It was specifically intended to be used for generated content primarily for autobuilders :) -- Christopher Larson
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
