[meta-freescale] [PATCH][fsl-community-bsp-base] setup-environment: provide a MACHINE menu

Daiane.Angolini at freescale.com Daiane.Angolini at freescale.com
Thu Mar 27 12:23:54 PDT 2014

> -----Original Message-----
> From: Trevor Woerner [mailto:trevor.woerner at linaro.org]
> Sent: Thursday, March 27, 2014 4:02 PM
> To: Angolini Daiane-B19406; meta-freescale at yoctoproject.org
> Subject: Re: [meta-freescale] [PATCH][fsl-community-bsp-base] setup-
> environment: provide a MACHINE menu
> On 03/27/14 14:08, Daiane.Angolini at freescale.com wrote:
> >> Traditionally I've been hesitant to send patches, but I've decided to
> >> not be as shy anymore. Therefore I don't expect everything I send to
> >> be successful :-)
> > Yes, please, don't be shy anymore and send all patches you have ;-)
> The can of worms is now open :-)


> > 2) it only list machines from meta-fsl-arm and meta-fsl-arm-extra. I
> > tried
> >
> > MACHINE="qemuarm" source setup-environment build
> >
> > And I faced a big error message!
> Whoops! I hadn't tested the emulators, but I agree they should certainly be
> in the list too. Getting a big error message isn't what I wanted to have
> happen.
> > I´m not sure if we want to list external boards, but it looks weird to me
> not being able to have a qemu build dir.
> By "external boards" I assume you mean non-ARM or non-freescale boards
> (e.g. beagle)? If so, I don't think we should worry too much about listing
> external boards, setup-environment comes from a freescale-specific
> repository. If someone is following the steps to checkout and build for a
> freescale board (and therefore using setup-environment), I think it's a
> safe enough assumption they're going to want to build for one of the boards
> supported by the freescale BSP repositories (or qemu). I don't think it's
> too much to say that someone would be in the wrong place if they were
> complaining that the freescale setup script didn't include options to build
> for a MIPS64 target :-)
> In other words, I believe the setup-environment script provided in fsl-
> community-bsp-base is already freescale-specific. Making it more so
> shouldn't be a problem?

And in the case a user has its own customer layer /inside/ fsl community bsp environment with a custom board?
Would this case be possible?


More information about the meta-freescale mailing list