[petsc-dev] CFLAGS and COPTFLAGS

[Jed Brown]

Matthew Knepley <knepley at gmail.com> writes:
> I am a fan of our current organization, which is the right mix of
> flexibility and performance. I don't think we can do much better,
> since we are stuck with the crap command line interface to compilers.

I brought the issue up because I noticed yet another user putting
optimization flags in CFLAGS and having it do nothing.  And I myself
recall confusion attempting to set flags and having them be ignored.
And the fact that it takes minutes to find out if your options were used
is extremely frustrating.

This is actually one point where the CMake GUI or curses interface is
helpful.  The default flags get plopped into the field and the user can
edit as they see fit without needing to second-guess the system.  Of
course non-interactive configuration can't do this except to run the
entire configure and copy out the default flags.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140117/156c50be/attachment.sig>