[vtk-developers] PREPENDING extra compiler flags?!?!

[Volpe, Christopher R (CRD)]

> -----Original Message-----
> From: Bill Hoffman [mailto:bill.hoffman at kitware.com]
> Sent: Tuesday, January 23, 2001 3:30 PM
> To: Volpe, Christopher R (CRD); Vtkdevelop (E-mail)
> Subject: Re: [vtk-developers] PREPENDING extra compiler flags?!?!
> 
> 
> The trick would be to edit getclasses.cxx and rebuild 
> pcmaker.  I don't
> see what harm would be done if the those flags were first all 
> the time.
> 

Yeah, I figured that might be the way to go. I was hoping for something less invasive, since I can't
be 100% sure what people are relying on (and changing this could stop builds dead in their tracks). I
probably couldn't indiscriminately move user-specified flags in front of everything else. Even I
count on the existing behavior, a little bit, so that my explicit "/O2" comes after, and overrides,
the generated "/Od" so that I can generate inline functions even in my debug code. Basically, as a
general rule, the user should be able to override default options. But in some cases (like /Od)
overriding means "comes after", whereas in other cases (like /I), overriding means "comes before".
I'll putz around a bit with user.make to see if I can solve my problem locally without impacting
anything else (unless there is a consensus that this would be a beneficial change anyway) before
modifying getclasses.cxx.

thanks,

Chris