[Petsc-trilinos-discussion] Scope and requirements

[Jed Brown]

"Bartlett, Roscoe A." <bartlettra at ornl.gov> writes:
>  [Bartlett, Roscoe A.] Does the PETSc build system support 100%
>  correct automatic incremental rebuilds when upstream dependencies for
>  these downloaded packages change?  Does it do a 100% correct
>  incremental rebuild when just a few files in the downloaded package
>  change?  That is the problem.  Anyone can create a build system that
>  does a one pass configure, build, and install from scratch.  The
>  problem is supporting an efficient development process where bits and
>  pieces are incrementally changing.  We take that for grated in a
>  unified CMake system.

1. PETSc's build system only does incremental rebuilds of PETSc, not of
other packages that it might use.

2. It takes 60 seconds to do a full (non-incremental) rebuild of PETSc
on a typical laptop.

3. If you use shared libraries (very common for development), it is
enough to rebuild libpetsc.so.  (PETSc binary interfaces only change
when source interfaces change, so you can go all year without needing to
relink.)
-------------- 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-trilinos-discussion/attachments/20131122/577c9052/attachment.pgp>