Check for compiler switch in code

I've written a Unit testing framework for an embedded system that reports the location of tests using __FILE__ and __LINE__. This is all well and good, except I also want to run the code on Visual Studio.

Now microsoft, in their infinite wisdom, change the meaning of __FILE__ depending on other compiler switches. For example if /Zi (note case of 'i') is defined __FILE__ is the relative path (to the project), but if /ZI is defined __FILE__ is the absolute path!!! :mad: (these, btw, defined the debugger database format. Imagining how that relates __FILE__ fills with horror)

The path needs to be absolute so our reporting tools can load those files. so I'd like to force users to specify /FC (an undocumented switch that creates absolute paths :rolleyes: ). I tried:

Code:

---

#if defined(WIN32) && !defined(FC)
#error Please add /FC to your compiler options
#endif

---

but unfortunately that doesn't work. Anyone know a way that does? and yes, I've STFW... :p

I don't think a command line switch is the same as a #define.

Code:

---

#if defined(WIN32) && !defined(FC)
#error Please add /FC to your compiler options
#endif

---

FWIW:
http://predef.sourceforge.net/preos.html#sec22
http://predef.sourceforge.net/precomp.html#sec32

Quote:

---

Originally Posted by Dave_Sinkula

I don't think a command line switch is the same as a #define.

---

I know. But some compiler switches cause #defines (for example _MT is defined for mulit-threaded builds), I was just hoping this might be the case here. No biggie.

http://msdn2.microsoft.com/en-us/lib...2s(VS.80).aspx
Doesn't look like it defines anything. But seems there is a way in managed code to do it.