Is it possible to use system or project macros within code?

Follow

Darcy Williams

• February 18, 2010 22:58

For example, we have three project configurations:  Dev_Debug, Dev_Release, Formal_Release.

Every one of our projects/products has these configurations.  Is there a way to use $(Configuration) within code so that I can then make slight code changes based on the build type?

e.g.

var build_type;

#if $(Configuration) == "Dev_Debug"

build_type = 'B';

#elseif $(Configuration) == "Dev_Release"

build_type = 'D';

#elseif $(Configuration) == "Formal_Release"

build_type = 'R';

#endif

 

I know the above method won't work, it's just an example of what I'd like to achieve, the exclusion/inclusion of code sections.

There seems to be a similar application here http://rowley.zendesk.com/forums/56662/entries/111211-get-the-build-date-and-time-from-within-my-program but I can't quite figure out how to use the $(Configuration) macro using the above sort of method.

Any ideas?

Thanks

0

• 

  Kelly Painter

  • February 19, 2010 00:53

  Could you use the project properties Preprocessor Options -> Preprocessor Definitions and define DEV_DEBUG, etc for each configuration? Then you could use #ifdef DEV_DEBUG ...

  0

  Comment actions Permalink
• 

  Darcy Williams

  • February 19, 2010 02:48

  Yes, that's kind of a last resort though due to the number of projects I'd need to go through and make all those changes to.  But yes, that's one way to do it.  The functionality appears to be available in CrossWorks, I'm just not sure if it'll let me do it this way  :-)

  0

  Comment actions Permalink
• 

  Jon Elliott

  • February 19, 2010 10:20

  As long as your configuration names don't have any spaces in them (which appears to be the case), you could do something like add a "CONF_$(Configuration)" preprocessor definition. Then you could use the following code:

  #if defined(CONF_Dev_Debug)

  ...

  #elif defined(CONF_Dev_Release)

  ...

  #elif defined(CONF_Formal_Release)

  ...

  #endif

  0

  Comment actions Permalink
• 

  Darcy Williams

  • February 19, 2010 21:22

  Thanks Jon.  That's an interesting twist on the prepro definitions method.  Bugger all difference in work (since I'd still need to edit every project rather than just a single shared source file) but I like the idea

  0

  Comment actions Permalink

Please sign in to leave a comment.