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

Barry Smith bsmith at mcs.anl.gov
Mon Oct 4 16:01:03 CDT 2010

On Oct 4, 2010, at 3:58 PM, Jed Brown wrote:

> On Mon, Oct 4, 2010 at 22:53, Barry Smith <bsmith at mcs.anl.gov> wrote:
>> Why? It takes less than 3 seconds on my laptop to generate everything.
> It's not the generating, it's recompiling all those files.  The cmake
> build (and builder.py now, sort of) keeps track of dependencies, so
> they only recompile files that have actually changed.  So it's the
> difference between 30 seconds to recompile all the auto stuff that has
> just had mtime updated (but identical content) and 3 seconds to
> recompile the two files that actually changed and relink libpetsc.so.
> Jed

  Then just have the fortranstubgenerate.py set the time of the generated files to the time of the underlying c file. No fancy code to decide if each file gets rebuilt but still won't require cmake complete compiles.


More information about the petsc-dev mailing list