6 months, 1 week ago.
Why is the 'ide' set with 'config' not used by 'export' command in mbed CLI?
We can set
mbed config ide [selelected IDE] mbed config target [selected target]
export does not use the
ide set with
config and commands like below fail
mbed export -m LPC1768
target set with
config works fine. For example
mbed export -i gcc_arm
I think in real life users usually use only one IDE and several targets. So it would be more pratical to be able to omit the
ide than the
target. Otherwise what's the point of setting the
config (what is it used for)?
5 months, 3 weeks ago.
That's a good observation! I think at one point this was supported but it no longer is. If you run the command with
--help we report that we only support
mbed config --help usage: mbed config [-h] [-G] [-U] [-L] [-v] [-vv] [var] [value] Gets, sets or unsets mbed tool configuration options. Options can be global (via the --global switch) or local (per program) Global options are always overridden by local/program options. Currently supported options: target, toolchain, protocol, depth, cache
So we let other options to be set, but they won't have any effect.
We'll check with the developers if there's more to the story and report back if there is.
Ralph, Team Mbed