Mbed-os: "missing mbed_config.h"

[ConductedForce]

Problem: make complains of "missing mbed_config.h" file. Makefile build fails.

How to reproduce:
Import Mbed library from github.
Export project using Make_GCC_Arm toolchain (Mbed Online Compiler).

Workaround:
This line in the ASM flags section:
ASM_FLAGS += /filer/workspace_data/exports/1/14a3ae37f9afc4a0299b9a8b5904f796/MyEmbeddedProject/mbed_config.h
seemed to be the problem.

I removed what seemed to be the internal file directory part until it was just: ASM_FLAGS += mbed_config.h

This fixed the problem for me. Project exporter for online version seems broken, at least for that toolchain.

[theotherjimmy]

@ConductedForce I think I fixed this a while ago. Could you try again?

[dorduran]

The same issue is exist for "Eclipse-GCC-ARM" exports (even with "mbed-os-example-blinky"). The build ends up with "mbed_config.h: No such file or directory".

Expected that all the export variants are being tested for error free builds automatically by Continuous Integration framework prior to any release.

[0xc0170]

Expected that all the export variants are being tested for error free builds automatically by Continuous Integration framework prior to any release.

http://mbed-os-ci.s3-website-eu-west-1.amazonaws.com/?prefix=jenkins-ci/artifacts/9252/1/exporter/PASS/gnuarmeclipse/ - one of the latest tests for exporters. It passed.
How to reproduce "Eclipse-GCC-ARM" exports - can you share steps to locally reproduce this failure?

[theotherjimmy]

@0xc0170 That's not eclipse_gcc_arm that's gnuarmeclipse, further this is an online-compiler-only problem.

[dorduran]

To generate,

Use the program "mbed-os-example-blinky" in the online compiler.
Target platform is "NUCLEO-F429ZI"

Export the program;
"Export Target:" "NUCLEO-F429ZI"
"Export Toolchain:" "Eclipse-GCC-ARM"

The export process generates;
"mbed-os-example-blinky_eclipse_gcc_arm_nucleo_f429zi.zip" package

Build the unzipped source tree and build in Eclipse.

The issue is in the "makefile" of the package;
Line 1284
...
ASM_FLAGS += /filer/workspace_data/exports/e/e0407cb4f27d2da7a57215e694d22171/mbed-os-example-blinky/mbed_config.h
...

To fix the issue, replace the line with;
...
ASM_FLAGS += mbed_config.h
...

Hope these help...

[theotherjimmy]

Thanks @dorduran. I need to build an offline test case that has the same property as your online steps so that we fix this and it stays fixed.

[zepperik]

I ran across this same problem when exporting for Qt Creator. Mine said "ASM_FLAGS += /filer/workspace_data/exports/8/85efb301d9f8fb7d8946bc28825cb708/rtos_semaphore/mbed_config.h". I changed it to just mbed_config.h.

[ConductedForce]

Just did a fresh export for a new project on the online compiler. Eclipse_GCC_ARM this time, fixed by deleting until just mbed_config.h .

[rkreifeldt]

I just ran into this same issue today. I am exporting to Eclipse-GCC-Arm
But for me I changed the line to:
ASM_FLAGS += ../mbed_config.h

[mjm2017]

The same ... NUCLEO_L476RG - ARM GNU MAKE still the export has that problem.

[choeecs27]

For my case, I replaced with the following and it would continue the build (but eventually failed for something else)
ASM_FLAGS += ../mbed_config.h

[ktuulos]

This problem still exists, and it can be still corrected with the same instruction.

For a newbie, who just downloaded "mbed-os-example-blinky" to Eclipse, this is quite a problem. Please, increase the priority for this problem.

[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/IOTOSM-2161