Added list options for --supported command

[mbartling]

Description

Added the ability to list toolchains, ides, and targets in addition to just dumping them as a matrix. This is useful for bash tab completion and other piping.

Status

READY/IN DEVELOPMENT/HOLD

Migrations

If this PR changes any APIs or behaviors, give a short description of what API users should do when this PR is merged.

NO

Todos

• Tests
• Documentation

[bridadan]

Hi @mbartling, this will definitely be useful. Would you mind posting an example of how to use the new options and their output? I'm not as familiar with the nargs="?" option for argparse.

[adbridge]

@mbartling please update the PR title to be more meaningful.

[mbartling]

@bridadan The nargs="?" and addition of the const value is so I don't break backwards compatibility. The former specifies that there are 0 or 1 arguments following the target subcommand. So the signature of the command line interface becomes
make.py [-S|-supported [toolchains|targets]] ...

Here is a high level example (using mbed cli):

$ mbed compile --supported toolchains
> GCC_ARM
> IAR
> ARM
$
$ mbed compile --supported
> [ORIGINAL_MATRIX]

Here is an example using mbed-os tools directly

$ python tools/make.py --supported toolchains
> GCC_ARM
> IAR
> ARM

[bridadan]

Ah ok I seem thanks for explanation. I only ask because I don't think nargs='?' is used anywhere else in the tools. But this is really good to know and use in the future! I didn't even know this capability existed 😄

[bridadan]

/morph test

[mbartling]

morph test? is that part of the test harness?

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1731

All builds and test passed!

[bridadan]

morph test? is that part of the test harness?

Yes 😄 (see above)

[bridadan]

@0xc0170 Everything seems good to my eye

[bridadan]

Actually crud, just remembered this touches exporters too.

/morph export-build

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 141

Exporter Build failed!

[bridadan]

Ok, so this failure was due to the fact the nrf52840 CMSIS pack wasn't present on the CI machines. I just added it now so we SHOULD be good to go. Running again...

Getting ahead of myself, #4021 needs to come in first.

[0xc0170]

/morph export-build

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph export-build

[bridadan]

@mbartling Can you resolve the conflict? We will rerun the CI after

[0xc0170]

Merge branch 'master' into supported-lists

Please rebase, do not merge if possible?

[mbartling]

@0xc0170 rebased with master

[bridadan]

@0xc0170 --list is only used internally in test.py, we don't actually use it anywhere else. --supported is used to tell you what you can supply to the required arguments like --target(-m), --toolchain(-t), --ide(-i), etc. --list is an action that gives you information on what test cases are available given a -m and a -t.

TL;DR they are separate options with two important purposes 😄

[bridadan]

I've restarted the last Jenkins on this PR. Hopefully we can finally get this merged!

[mbartling]

@bridadan @0xc0170 bump :)

[bridadan]

I'm assuming a merge party will happen around the time of the release of 5.4.3, so get ready 🎉 🎈

[sg-]

/morph export-build

[mbed-bot]

Result: ABORTED

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 157

Example Prep failed!

[bridadan]

/morph export-build

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 158

All exports and builds passed!

[mbartling]

🕺 🎉 🌮

[bridadan]

@0xc0170 Hopefully this can get in before something else blocks it 😛

[theotherjimmy]

@bridadan got your back

[ohagendorf]

This PR was merged but didn't get a label in which release version it is planned to be added?
Is it not decided or is it maybe forgotten?

[theotherjimmy]

Thanks for the reminder @ohagendorf

[adbridge]

This change relies on #3997 which is marked to go in for 5.5.0, thus relabeling this one accordingly.