Blinky baremetal fails to compile due to config problems with Nanostack

[MarceloSalazar]

Description of defect

Few targets that support Nanostack drivers with RTOS fail to compile blinky-baremetal.

The targets shouldn't fail to compile The Nanostack component should be ignored as are not included in the bare-metal app.

Target(s) affected by this defect ?

KW41

 [Fatal Error] NanostackRfPhyKw41z.cpp@17,10: common_functions.h: No such file or directory
    [ERROR] ./mbed-os/features/nanostack/targets/TARGET_NXP/TARGET_KW41Z/NanostackRfPhyKw41z.cpp:17:10: fatal error: common_functions.h: No such file or directory
    17 | #include "common_functions.h"

TB_SENSE_12

    [Fatal Error] NanostackRfPhyEfr32.cpp@22,10: 'ns_types.h' file not found
    [ERROR] ./mbed-os/features/nanostack/targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/NanostackRfPhyEfr32.cpp:22:10: fatal error: 'ns_types.h' file not found
    #include "ns_types.h"

Toolchain(s) (name and version) displaying this defect ?

Arm Compiler 6 and GCC 9

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.0.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed CLI 1.10.4

How is this defect reproduced ?

mbed import https://github.com/ARMmbed/mbed-os-example-blinky-baremetal
cd mbed-os-example-blinky
mbed compile -t <toolchain> -m <target>

@ARMmbed/mbed-os-maintainers

[ciarmcom]

@MarceloSalazar thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. '(d0d35c2)' has not been matched as a valid tag or sha.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[LDong-Arm]

The main issue is that mbed-os/features/nanostack/targets/TARGET_* are not guarded by any mbed_lib.json - they are always visible to the build, if your target is one of them.

I create #13119 to resolve this. Now the blinky-baremetal example compiles for KW41Z.

As for TB_SENSE_12, this target doesn't currently support bare metal. The new error (after the fix) is now the same as any other target that doesn't support bare metal, until we implement a more user-friendly error handling for this. This is not part of this GitHub issue then.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2712