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

[Daiane.Angolini at freescale.com]

> -----Original Message-----
> From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On
> Behalf Of Otavio Salvador
> Sent: Thursday, March 27, 2014 4:38 PM
> To: Angolini Daiane-B19406
> Cc: Trevor Woerner; meta-freescale at yoctoproject.org
> Subject: Re: [meta-freescale] [PATCH][fsl-community-bsp-base] setup-
> environment: provide a MACHINE menu
> 
> On Thu, Mar 27, 2014 at 4:25 PM, Daiane.Angolini at freescale.com
> <Daiane.Angolini at freescale.com> wrote:
> > When you have 150 imx6 boards, this cluttering is not enough and you must
> find a second level.
> >
> > The second level would ~naturaly~ be meta-fsl-arm/extra (naturaly
> > because they are 2 separate layers)
> >
> > In other hand, I don´t think the clustering approach is the right one
> > to go
> 
> Yes; or in future we may group it by vendor.
> 
> Freescale
> ...
> 
> Boundary Devices
> ...
> 
> SolidRun
> ...
> 
> OLIMEX
> ...
> 
> I am just thinking if it is overkill or not.
> 
> Another solution is:
> 
> * if machine is set, use it
> * if machine is not set:
>   - Ask user to go to release notes and choose the machine

I prefer the list of alphabetically sorted 150K machines instead of "go to release notes" approach.

Let´s get is simpler instead of more complex. No need for external sources/infos


Daiane

>   - call again with MACHINE=foo
> 
> ?
> 
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>