This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/13077] Need a way to disable warnings in code
- From: "tron dot thomas at verizon dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Nov 2003 00:10:35 -0000
- Subject: [Bug c++/13077] Need a way to disable warnings in code
- References: <20031116172820.13077.tron.thomas@verizon.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From tron dot thomas at verizon dot net 2003-11-17 00:10 -------
Subject: Re: Need a way to disable warnings in code
Thanks pinskia. I did not know about that. I'm glad there is a way to
deal with per module settings.
I still don't know how helpful it is because the warning is actually
generated in a header file, and knowing all the module that would be
affected by the header is a little tricky.
I've dealt with the problem by stubbing an extra, unnecessary function
into class that will eliminate the warning when building with GCC. This
will work fine for me.
pinskia at gcc dot gnu dot org wrote:
>------- Additional Comments From pinskia at gcc dot gnu dot org 2003-11-16 22:43 -------
>What you said about "Project Builder" is not true, it has not been true for the past year.
>Yes it is hard to find where to put per file flags but you can do it.
>Go to the target settings.
>Click on Sources under "Build Phase".
>Click on the file you want to add the flag.
>Click on the left most part of the field and this will bring up a window where you can put the extra
>flag.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13077