[meta-freescale] [PATCH][fsl-community-bsp-base] setup-environment: provide a MACHINE menu
otavio at ossystems.com.br
Thu Mar 27 11:17:31 PDT 2014
On Thu, Mar 27, 2014 at 3:08 PM, Daiane.Angolini at freescale.com
<Daiane.Angolini at freescale.com> wrote:
> Yes, please, don't be shy anymore and send all patches you have ;-)
> I like your patch. But it have several important problems.
> 1) assign a number to a board may lead user to error. I love the machine list, and I love that imx53qsb is 20, but when a new board is added I will try to use 20 and it will not be imx53qsb. This is only one example, and this only happens if you use a dynamic order for the machine list.
> 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!
Agreed this is not user friendly heh...
> 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.
Good point. Even though we may not list the other machines I think it
is expected those to me usable.
> 3) In error message, instead of list all boards one before the other, list one machine per line.
> I like to prompt user instead of assuming a default machine. But a list of machines is not good when you have 150 machines. And I start to try to group the machines in SOC family, or in meta-fsl-arm/meta-fsl-arm-extra, or any other criteria to help user to decide it.
I am a bit unsure we ought to do a list by default. Maybe one more
user friendly way is:
* If no machine is set (using MACHINE=foo source ./setup-environment
build-foo), say to run ./setup-environment list-machines
* If user sets the machine, use it
* If user runs ./setup-environment list-machines, a list of machine
plus its verbose description might be output and use the 'more -d'
trick as EULA to paginate it.
Otavio Salvador O.S. Systems
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
More information about the meta-freescale