[petsc-users] maintaining application compatibility with 3.1 and 3.2

[Kirk, Benjamin (JSC-EG311)]

On Apr 17, 2013, at 9:20 AM, "Kirk, Benjamin (JSC-EG311)" <benjamin.kirk-1 at nasa.gov> wrote:

> On Apr 17, 2013, at 9:12 AM, "Alexei Matveev" <alexei.matveev at gmail.com> wrote:
> 
>> Do you maybe have any tips or pointers on how to maintain such a
>> compatibility?
> 
> We have a collection of macros that we use in the libMesh project to aid with this - see in particular petsc_macro.h at http://libmesh.sf.net.
> 
> We test daily with petsc 3.0 to 3.3 using this approach. 
> 
> Ill get you the precise link if you desire later…

See the macro definition here:
http://libmesh.sourceforge.net/doxygen/petsc__macro_8h_source.php

For example, we define the macro LibMeshVecDestroy() as a wrapper to the version-specific PETSc implementation.

-Ben