You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This provides one approach to address cmake link mess with
mbed-core-flags/mbed-rtos-flags whose links or not depends on selected
application profile, full or bare-metal.
1. Add target config option application-profile for application to
select which application profile to use. Applications are responsible
for making this target config option consitent with link selection of
mbed-os/mbed-baremetal.
2. Overload mbed-core-flags/mbed-core-sources so that they can involve
mbed-rtos-flags/mbed-rtos-sources or not depending on
target.application-profile setting
Copy file name to clipboardExpand all lines: targets/targets.json5
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,14 @@
100
100
"semihosting-enabled": {
101
101
"help": "Enable ARM Semihosting protocol. This uses a magic breakpoint instruction to enable the MCU to print data to and access files on a host machine. However, it can interfere with debuggers that are not semihost aware.",
102
102
"value": false
103
+
},
104
+
"application-profile": {
105
+
"help": "Select application profile. Options: auto, full, bare-metal. 'auto' mode will check other build options and resolve to\
106
+
'full' mode by default or 'bare-metal' mode, for example, MBED_GREENTEA_TEST_BAREMETAL being ON for Greentea test. 'full' mode\
107
+
enables the real-time OS and enables all features of Mbed to be used. 'bare-metal' mode disables the real-time OS, preventing you\
108
+
from using threads and libraries that depend on them. 'bare-metal' mode is recommended for target MCUs with small amounts of flash\
0 commit comments