Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`mbed compile -t GCC_ARM -m K64F --tests` should set the default toolchain and target
See original GitHub issueDescription
- Type: Enhancement
Enhancement
Reason to enhance/problem with existing solution
If user compiled the code with explicit target and toolchain on command line:
mbed compile -t GCC_ARM -m K64F --tests
and run mbed test afterwards, the default target and toolchain would be used rather than the latest one. This behaviour would not be expected by the user.
Suggested enhancement
mbed compile -t GCC_ARM -m K64F --tests should set the default toolchain and target
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
warning The mbed tools were not found in .. - Question
in the command line, and it does not let me execute any command (nor mbed compile, nor mbed target, nor anything of it)...
Read more >Path to GCC_ARM (mbed_settings.py) - Stack Overflow
I've fixed my problem by installing these 2 repositories + my cmake was on pip3 strangely. It had install cmake with pip3 rather...
Read more >mbed-cli 1.8.3 - PyPI
Using mbed target <target> and mbed toolchain <toolchain> , you can set the default target and toolchain for your program. You won't have...
Read more >Using mbed with Kinetis Design Studio - Freedom To Play
A brief overview of building mbed locally and incorporating it with the Freescale Kinetis Design Studio.
Read more >Code Coverage for Embedded Target with Eclipse, gcc and ...
Instrument code: Compile the application files with a special option. This will add (hidden) code and hooks which records how many times a ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My recommendation is to only update the setting after a successful compile when the setting is not present. This would implicitly do validation with the build tools. Further it would reduce code duplication of validation between the mbedmicro/mbed tools and mbedcli. Alternatively, you could run tools/get_config.py with -t and -m to verify that the toolchain and mcu are supported/valid/not-a-typo.
Validation is needed before setting the default otherwise a typo could be come the default.