NCS1.3.0 --> MBEDTLS_CONFIG_FILE --> #include expects "FILENAME" or

[maddy5075]

NCS 1.3.0 mbedTLS configuration to the existing app in SES results in compilation error.

The SES project file contains the define like so -DMBEDTLS_CONFIG_FILE=\\"nrf-config.h\\"

[basvkesteren]

I'm running into the same problem, using ncs 1.3.1.

The fix in the linked post, both with 'PRIVATE NONE' 'and 'NONE PRIVATE' doesn't seem to make any difference. The fix from JeanFI from that same post doesn't fix the problem either.

About to figure out how to build a project from the command line (using segger embedded studio atm)...

[JeanFi]

Hi,

Yes my fix is clearly not enough.

Now we build/flash/debug in command lines. It is not difficult: see https://developer.nordicsemi.com/nRF_Connect_SDK/doc/0.4.0/zephyr/guides/west/build-flash-debug.html

Main commands we use:

west build -b yourboard

west flash

west debugserver

And we use Ozone J-Link Debugger (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/tools/nordic_segger.html#segger-ozone) to perform debug

Note:

The most important: to successfully execute west, open command prompt like this

[basvkesteren]

Yay, this works! Thanks!

Somehow i could not make west recognise my custom board, but the CMAKE/ninja command did work. I just peformed my first SHA-256 hash