[petsc-dev] make allfortranstubs

Barry Smith bsmith at mcs.anl.gov
Mon Mar 13 12:46:27 CDT 2017

> On Mar 13, 2017, at 8:55 AM, Jed Brown <jed at jedbrown.org> wrote:
> Matthew Knepley <knepley at gmail.com> writes:
>> Welcome to the hidden pain of PETSc development :) Here you must insert
>>  make allfortranstubs
> If we just make bfort refuse to overwrite files when its output is
> identical to the output on disk, then we could run it automatically when
> any source files change without incurring recompilation/relinking
> overhead.

   In other words, write to a file with an alternative name, diff between the files and mv over only if the files differ?

   Presumably portions of the process of making fortran stubs can be run in parallel so as to make the time less painful.

More information about the petsc-dev mailing list