[LukasK]

Okay sorry again. I just realized I used mbed-cli in the WSL… Thats why the path length was not a problem…

[LukasK]

I will test the new version right now.

If i use mbed-cli without visual gdb, i am able to run all my tests…
This is a path which is generated using visual gdb: Build\\WD_CORE_G1\\Tests__Debug_\\WdIoT.Firmware.Lib\\util\\ledsignaling\\TARGET_WD_CORE\\TARGET_WD_CORE_G1\\TESTS\\ledsignaling\\ledutils\\WdIoT.Firmware.Lib\\util\\ledsignaling\\TARGET_WD_CORE\\TARGET_WD_CORE_G1\\TESTS\\ledsignaling
As you might see WdIoT.Firmware.Lib\\util\\ledsignaling\\TARGET_WD_CORE\\TARGET_WD_CORE_G1\\TESTS\\ledsignaling\\ledutils gets concatenated twice. This doesnt happen if i use mbed cli only.

[LukasK]

I hope it’s okay if I keep posting new problems

User Defined Variables aren’t resolved for Terminal Settings (COM Port)

[LukasK]

And another problems occurs with testing.

Paths while building tests are getting to long for windows to handle. Is there any solution available?

[LukasK]

Thank you for you support. I realized and hadn’t installed the latest version.

Your comments fixed by problems. thank you.

But i have another question. Is there a possibility to add defines only for Testing?

[Author]

Posts