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

[Matthew Knepley]

On Tue, Oct 5, 2010 at 3:41 PM, Jed Brown <jed at 59a2.org> wrote:

> On Tue, Oct 5, 2010 at 17:18, Matthew Knepley <knepley at gmail.com> wrote:
> > Obviously not slower than building everything that gets touched.
>
> Get builder.py to rebuild after
>
> find src -name '*vec.c' | xargs touch
>
> in under 5 seconds and we'll talk.  It is still very slow.
>
> The correct thing is to have the build system manage generated files
> (instead of the configuration system), so they get updated exactly
> when needed.
>
>
> BTW, builder.py outputs things like the following, charges on, and
> then doesn't successfully create an archive.
>
> ERROR: Missing object file
> /home/jed/petsc/ompi/lib/libpetsc-obj/petscsnesmod.o
>

It does not do Fortran modules correctly because right now I cannot handle
that level
of wrongness.


> It also puts *.d files in the source tree, but these reference files
> in $PETSC_DIR/$PETSC_ARCH/include, and thus is incorrect if you have
> multiple arches.


True.

   Matt


>
> Jed
>



-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101005/ec21c6ea/attachment.html>