Groups > Borland > Borland C plus plus builder command line tools > Re: Compileroption for changing a warning to an error?




Compileroption for changing a warning to an error?

Compileroption for changing a warning to an error?
Fri, 30 Mar 2007 12:27:31 +020
Hello,

I'm using BDS2006 BCC32 V5.82, ILINK32 V5.70.

Is there a way to let the compiler stop at a specific warning instead of
just displaying it? Probably a compiler option like for example -we8030?

Kind regards

-Christian

Post Reply
Re: Compileroption for changing a warning to an error?
Fri, 30 Mar 2007 13:29:39 +020
Christian Killmann wrote:
> Hello,
>
> I'm using BDS2006 BCC32 V5.82, ILINK32 V5.70.
>
> Is there a way to let the compiler stop at a specific warning instead
> of just displaying it? Probably a compiler option like for example
> -we8030?

Such as:

  -w!     Return non-zero from compiler on warnings

Makes the build stop when using makefiles.

Ebbe 

Post Reply
Re: Compileroption for changing a warning to an error?
Mon, 2 Apr 2007 07:04:28 +0200
Hi Ebbe,

thanks for your reply. I tried -w! before posting to this newsgroup and
didn't manage to stop the compiler only on a specific warning. I think
that -w! just stops at every warning, and that is sadly no option for me. Or
am i just missing some tricky syntax?

Kind regards

-Chris

Post Reply
Re: Compileroption for changing a warning to an error?
Mon, 2 Apr 2007 15:27:27 +0200
Christian Killmann wrote:

> thanks for your reply. I tried -w! before posting to this newsgroup
> and didn't manage to stop the compiler only on a specific warning.

Sorry, I overlooked the "specific" part of it.

Ebbe 

Post Reply
Re: Compileroption for changing a warning to an error?
Mon, 2 Apr 2007 15:34:06 +0200
Christian Killmann wrote:

> thanks for your reply. I tried -w! before posting to this newsgroup
> and didn't manage to stop the compiler only on a specific warning. I
> think
> that -w! just stops at every warning, and that is sadly no option for
> me. Or am i just missing some tricky syntax?

I though a little more about it and came up with this workaround:

bcc32 <whatever> | grep -v "Warning 8030"

The -v option makes grep return a non-zero error code if it finds the 
warning in question.

Ebbe 

Post Reply
<< Previous 1 2 Next >>
( Page 1 of 2 )
about | contact