Which Complier is default used? Both SES and NCS

[Bee]

Hello everyone~

I'm now trying to use a third-party software (BSEC, Bosch Sensortec Environmental Cluster，a lib for gas sensor BME680). It limits the complier to arm-none-eabi-gcc. Is nRF5 SDK configed as arm-none-eabi-gcc by default? And is NCS configed as arm-none-eabi-gcc or clang by default?

[Hieu]

Hi,

The nRF5 SDK is in maintenance mode and we do not recommend any new project to use it.

And is NCS configed as arm-none-eabi-gcc or clang by default?

It uses arm-zephyr-eabi-gcc by default. However, the SDK supports BME680. I am guessing that you want to use a binary to work with the sensor here. It should work. Please refer to this past case.

Is nRF5 SDK configed as arm-none-eabi-gcc by default?

It depends on your environment. If you use Keil uVision or SEGGER Embedded Studio, then arm-none-eabi-gcc is used by default; note that it is meant to support and only tested with only a rather old version of the compiler.

You can also use a manually installed copy of arm-none-eabi-gcc and Makefile.

nRF5 SDK also supports IAR. I actually have never used IAR before, but it looks like it uses the IAR C/C++ Compiler.

Hieu

[Bee]

Thank you!