Hi Tim,

My project is a mixture of .ino and .cpp files and at the beginning of the main .ino file I have perhaps a dozen pre-processor defines of the form :

#define FEATURE_MINMAX true
#define FEATURE_ALARM false

which I use subsequently to either include or exclude pieces of code. The IDE handles this nicely and greys out the parts of code which are not to be included. 

Although the everything works as expected in the .ino files, it seems that the compiler does not handle the #defines properly in the .cpp files and always excludes my code - even though it is not greyed out by the IDE.

Perhaps this is expected behaviour - I'm not sure?? I can't see this explicitly stated in the documentation.

I have tried using the DEFINES field of the project properties to solve the problem. If I use   

FEATURE_MINMAX true;FEATURE_ALARM false; 

then the .cpp files appear to compile as expected but the IDE flags the following error on the first line of every file in the project :

command-line error: invalid macro definition: FEATURE_MINMAX true

The project seems to compile OK but I would like to get rid of these errors.

What is the recommended way of handling project wide #defines in these circumstances?? 

I find the DEFINES field of the project properties gets very unwieldly with 12 semicolon separated #defines in one long string. Is there a better way of doing this?

Thanks

n      

Hi,

Indeed the = removed the IDE errors.

I took a look at the compile patterns but I think that area is a bit beyond me for now. 

I have solved my problem by putting all the #defines into a separate file "Defines.h" and have included this where required. This avoids the ugly long DEFINES string in the project properties.

Thanks

n