[petsc-dev] [petsc-users] Override PETSc compile options

[Barry Smith]

  So why not just rename the strange PETSc variables by using the standard names prepended with PETSC_  this will be much clearer and is a simple etags refactorization of the code that should take just a few minutes (and since “no body uses these variables”) won’t even be noticed by anyone.

   Barry


On May 9, 2014, at 8:00 AM, Jed Brown <jed at jedbrown.org> wrote:

> Satish Balay <balay at mcs.anl.gov> writes:
>> At that time  - there was a percieved problem that got adressed.
>> 
>> If the naming schme was not consistant with a 'prefered' scheme - I guess it can be fixed.
>> 
>> No one [on the user side] used it or cared about it in past many years.
> 
> I try to write project makefiles that are agnostic to external
> libraries, rather than including PETSc "rules" (which I think are
> terrible).  These end up looking really fragmented when I define
> 
>  MYPROJ_CFLAGS = $(PCC_FLAGS)
>  MYPROJ_CPPFLAGS = $(CCPPFLAGS)
>  MYPROJ_CC = $(PCC)
>  MYPROJ_CCLD = $(PCC_LINKER)