emBuild configuration - global macro

RE: emBuild configuration - global macro

SLiuCognosos — Wed, 05 May 2021 14:21:57 GMT

Kind of...

I was trying out everything I could think of, and I did try something similar to what you discribed in the other reply. And got the same issue.

I also tried to see if the IDE can grab values from an OS environment var. However, the IDE's documentation on (what I think was) relevant parts is next to none.

If the -D option does not over-ride/create a new definition, then hopping through yet another pre-processor def only makes my project messier.

So what I decided to do was a python script that generates the "version" #define (you can put this into a "pre build" command), and use the "post build" to call another script (in my case, same script with a different option) to delete the "version" so that you won't be accidentally building a code that has wrong version info.

This is waaaay more convoluted that what I envisioned at first... but kinda works for the time being...

Word of caution: Cross building platform is another beast and my solution here does not play nice enough, at least across Win <-> Linux, but I didn't put too much effort in it...

RE: emBuild configuration - global macro

mtsunstrum — Tue, 04 May 2021 21:59:11 GMT

Quirky, but this looks like a way to do it ...

https://forum.segger.com/index.php/Thread/4785-SOLVED-EMBuild-D-option/

Only downside is if not using the embuild command-line (ie. using SES IDE), it is not clear what $(EXT_APP_VER) may default to.

The functionality works, but as expected, there seems to be a problem when using the same .emproject via the SES IDE.

If I setup up a preprocessor variable defined as follows:

MY_PREPROCESS_VAR=$(EXT_MY_PREPROCESS_VAR)

... then using -D EXT_MY_PREPROCESS_VAR=3 works fine.

BUT via SES IDE, the MY_PREPROCESS_VAR will exist, but I cannot test it as below .. because compiler / preprocessor will see MY_PREPROCESS_VAR defined as $(EXT_MY_PREPROCESS_VAR) and exit on a compile error.

#if defined(MY_PREPROCESS_VAR) && (MY_PREPROCESS_VAR == 3)

In the project, I can define a default project macro: e.g EXT_MY_PREPROCESS_VAR=2

... but here is the jist of the problem. This project macro value does not get over-ridden by -D EXT_MY_PREPROCESS_VAR=3

Grrr ...

RE: emBuild configuration - global macro

mtsunstrum — Tue, 04 May 2021 21:45:43 GMT

Seeing the same here. Did you find a solution ?

RE: emBuild configuration - global macro

Kenneth — Wed, 14 Apr 2021 16:04:20 GMT

Hi,

I think this question is best directed to SEGGER:
https://www.segger.com/support/technical-support/
https://forum.segger.com/

Kenneth