[petsc-dev] CFLAGS and COPTFLAGS

Jed Brown jed at jedbrown.org
Fri Jan 17 12:06:41 CST 2014


Satish Balay <balay at mcs.anl.gov> writes:

> On Fri, 17 Jan 2014, Jed Brown wrote:
>
>> As far as I know, this is not a widespread convention.  Lots of users
>> put in CFLAGS=-O3 and either don't notice that it doesn't get used or
>> are frustrated that it's not used.  Is the "auto" value of splitting out
>> COPTFLAGS worth this confusion?  Or can we make the behavior more
>> obvious?
>
> This is primarily required for the option --with-debugging=0/1 [which
> is also not a convention used by other packages]

It's not uncommon to have such a flag to enable debugging _code_ within
the library.  IIRC, it usually implies adding a debugging flag unless
the user specifies CFLAGS themselves.
-------------- 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/76a42624/attachment.sig>


More information about the petsc-dev mailing list