[petsc-dev] Could generatefortranstubs.py be lazier about modification times?

[Jed Brown]

On Mon, Oct 4, 2010 at 23:26, Satish Balay <balay at mcs.anl.gov> wrote:
> Hmm - if there is a file 'xxx.c' - then bfort generates ftn-auto/xxxf.c

It looks like generation of include/finclude/ftn-auto/*.h90 is much
less direct.  The dependencies below also produce unused *.h90 files.
What is bfort using to produce these f90module.f90 files?  Do you
think it's feasible to get a list of files that each *.h90 depends on?
 If not, I guess I'll just live with the few seconds to recompile
these and relink even though nothing changed.

Jed

src/sys/plog/f90module.f90 -> include/finclude/ftn-auto/petscprofiling.h90
src/sys/verbose/f90module.f90 -> include/finclude/ftn-auto/petscprofiling.h90
src/mat/order/f90module.f90 -> include/finclude/ftn-auto/petscmatorderings.h90
src/mat/matfd/f90module.f90 -> include/finclude/ftn-auto/petscmatfd.h90
src/mat/partition/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/mat/partition/impls/party/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/mat/partition/impls/chaco/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/mat/partition/impls/jostle/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/mat/partition/impls/pmetis/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/mat/partition/impls/scotch/f90module.f90 ->
include/finclude/ftn-auto/petscmatorderings.h90
src/characteristic/interface/f90module.f90 ->
include/finclude/ftn-auto/petscsemilagrange.h90