[petsc-dev] Fortran stubs

[Satish Balay]

On Thu, 19 Dec 2013, Barry Smith wrote:

> 
> On Dec 19, 2013, at 1:52 PM, Matthew Knepley <knepley at gmail.com> wrote:
> 
> > is there a good reason not to add rules for all the fortran stubs with the right dependencies, and call bfort individually?
> 
>    Can all the generated files also go in ${PETSC_ARCH} instead of within the source code so that I can have different branches with different arches and switch between them without having to regenerate (and remove) the fortran stubs appropriate for that particular arch — branch.

One issue is distributing and compiling sowing.

For ex: on windows it currently builds with g++ [not MS C]. And on big
machines [and batch systems] we don't want to be building it with
mpicc.

Satish