[petsc-dev] Fortran stubs

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:

> 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.

I would greatly prefer both of these, but I don't know how hard it is to
add to bfort.  I think the dependency rules are not complicated for the
ftn-auto stubs, though f90 interfaces seem messy.
-------------- 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/20131220/ecb23bed/attachment.sig>