[Cmake] RE: suppressing warnings on bcc

[Wheeler, Frederick W (Research)]

Andy,

It seems to me that something like COMPILE_POST_FLAGS would work nicely in
this situation.  If that were implemented, COMPILE_FLAGS could become a
synonym for COMPILE_PRE_FLAGS.

COMPILE_FLAGS_OVERWRITE seems dangerous to me.  Personally I would avoid it
because it seems that CMake adds a lot of options that are required and that
I would not want to mess with.

Regards,
Fred




> -----Original Message-----
> From: Andy Cedilnik [mailto:andy.cedilnik at kitware.com]
> Sent: Tuesday, February 24, 2004 10:50 AM
> To: Wheeler, Frederick W (Research)
> Cc: CMake List (E-mail); 'Ian Scott'
> Subject: RE: [Cmake] RE: suppressing warnings on bcc
> 
> 
> Hi Fred,
> 
> I see. What you would really need is something like:
> 
> COMPILE_FLAGS_OVERWRITE
> 
> or 
> 
> COMPILE_PRE_FLAGS and COMPILE_POST_FLAGS
> 
> The first one would overwrite default C/CXX flags with this 
> ones, while
> the second one would prepend or append flags.
> 
> Any comment?
> 
> 			Andy
> 
> On Tue, 2004-02-24 at 10:44, Wheeler, Frederick W (Research) wrote:
> > Thanks for the answer, but we are currently using
> > SET_SOURCE_FILES_PROPERTIES just as you suggest and having 
> this problem with
> > the option order on the compile command line.  
> > 
> > I should not have even mentioned these following 3 lines.  
> They are a red
> > herring and make my last e-mail unclear.  All I was saying 
> is that this
> > technique works fine elsewhere in VXL - it gets the option 
> order right, but
> > it adds the option for all files.
> > 
> > > >   IF (BORLAND)
> > > >     SET (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -w-8004")
> > > >   ENDIF (BORLAND)
> > 
> > When Ian does the following, which is what you are 
> suggesting (right?), the
> > warnings are not suppressed because of the compile command 
> line option order
> > issue shown in my previous e-mail. (in the Makefile stanza part)
> 
>