How to add preprocessor macros in VS code with NCS.

[Frikkie Badenhorst]

Hi there,

We are quite new to Zephyr. We are currently porting our existing app onto Zephyr as a test. We are currently using NCS 2.5.1

So for our existing application running in IAR, we have different build configurations. The one build configuration is "debug", in which serial logging and other debugging tools is enabled. The other build configuration is release, which is optimized and does not include debugging tools like serial logging in the build (does not configure the uart or use it ever).

For the different build configurations, we then provide different preprocessor macros, for example RELEASE for the release build and DEBUG for the debug build. In the code then, we can use the following:

 #ifndef RELEASE
    //Do something for DEBUG build
 #else
    //Do something for RELEASE build
 #endif

\

However we cant seem to provide preprocessor macros, unless we are overlooking it. I cant imagine that it is not possible to do this. So in the above statement, the #else clause is always true since RELEASE can never be defined.

Does not seem to be easy to have different project settings for different build configurations, as changing the proj.conf and cmakelists.txt file seems to change settings project wide (on all build configs).

Regards,

Frikkie

[Frikkie Badenhorst]

runsiv said:

Update: I got a coworker to test the same Cmake flag and it works on their computer. So You need to write -DVARIABLE=y in the add extra cmake argument  and it should work. 

By -DVARIABLE=y I assume you mean -DENABLED=y as in your example? If that is the case, this solution is not working on my side as I have explained in my previous post:

Frikkie Badenhorst said:

ENABLE_SOMETHING is not defined, the Q_DEFINE_THIS_MODULE(main) function should be called:

I then add an extra CMAKE argument:

However, we still get a build error on the line "Q_DEFINE_THIS_MODULE(main)", even though it should not be compiled in. You can also see from the first screenshot that intelli-sense does not grey out the line, indicating the macro is not seen.

Note the "y" instead of y was automatically added by the extension

[runsiv]

Interresting, It was the same thing that I saw on my computer while my coworker did not get the ""

I will investigate a bit

Regards

Runar

[runsiv]

I will check and get back to you

[Frikkie Badenhorst]

I look forward to hearing back from you!

[Frikkie Badenhorst]

Do we have an update here?