I've got a third-party library that generates a ton of warnings, even under /W3. Is there a way for me to tell the compiler, "disable C4244 for any file included from this directory, or its subdirectories"? Of course, I don't want to disable the warning in our own codebase, nor do I want to have to track down every possible include and wrap it with #pragma warning(...
views:
82answers:
4
+1
Q:
Can you turn off (specific) compiler warnings for any header included from a specific location?
A:
I'm not sure whether you meant you do not want to wrap your include statements with #pragma directives or did not want to spend time tracking down the right directive. If its the latter, then this is what I've done in the past:
#ifdef _MSC_VER
#pragma warning( disable : 4244 )
#endif
#include "MyHeader.h"
#ifdef _MSC_VER
#pragma warning( default : 4244 ) /* Reset to default state */
#endif
Regards, Ashish.
Praetorian
2010-07-17 17:59:47
Sorry, it was the former. I know how to disable warnings through #pragma already.
mos
2010-07-17 18:17:38
This should work. The compiler memorizes the warning pragma that was in effect when it compiled the declaration.
Hans Passant
2010-07-17 18:29:25
@Hans: This might turn off the warnings generated by MyHeader.h, but it doesn't answer my question. I don't want to search a couple hundred files for the several dozen library includes, and then wrap them with the #pragmas.
mos
2010-07-17 18:53:13
@mos: why do you have to search? The compiler reminds you that you missed one.
Hans Passant
2010-07-17 18:54:54
Praetorian
2010-07-17 22:55:19
+1
A:
You could try removing the 3rd party project from your include path. Then create a sub-dir that has the same dir structure and header files as the 3rd party project, so that all of the #includes now find your headers instead. Then in each fake header xxxx.h you set the pragma's then include the real xxxx.h header, then clear the pragma. To avoid recursively including the same file you would have to add an extra dir to the #include.
Personally, I'd just go through your project and add the pragma's.
jon hanson
2010-07-17 19:58:22
A:
You can put flags e.g /wd4600 in VS Project Settings > Command-line Options to tell the complier to suppress specific Complier Warnings
Dave18
2010-07-17 20:32:36
This misses the part that he says about, "I don't want to disable the warning in our own codebase."
Brooks Moses
2010-07-18 00:23:58
A:
I hate to answer my own question here, but I'm afraid that the "correct" answer in this case is: it's not possible.
mos
2010-07-21 19:01:17
@mos Yes. I've even tried to abuse the pre-processor to generate a INCLUDE macro that disabled warnings but that doesn't seem possible also. The only way out to have some sensible output I think is to grep the compiler warning output but for now I'm just living with all warnings.
Vitor Py
2010-07-21 21:43:50