[petsc-dev] PETSc always recompiles mpi4py petsc4py even when it does not have too
Satish Balay
balay at mcs.anl.gov
Sun Oct 11 13:46:04 CDT 2020
Which is the correct thing to do. i.e:
if libpetsc.so is rebuilt - its dependencies should get rebuilt.
However - in cases where it doesn't get rebuilt (as make found no new
sources to compile) - its probably best to add infrastructure to skip
the rebuild of dependent packages.
Satish
On Sun, 11 Oct 2020, Pierre Jolivet wrote:
> This actually applies to all packages with builtafterpetsc = 1.
> I think you want to do make libs instead of make all?
>
> Thanks,
> Pierre
>
> > On 11 Oct 2020, at 9:36 AM, Barry Smith <bsmith at petsc.dev> wrote:
> >
> >
> > I change a single PETSc file and do make all that single file gets compiled but all of mpi4py and petsc4py get recompiled even though I have not changed any thing to affect them. No include files for example
> >
> >
> > *** Building mpi4py ***
> > *** Installing mpi4py ***
> > =====================================
> > To use mpi4py, add /Users/barrysmith/Src/petsc/arch-cleanup-dmd-domaindecomposition/lib to PYTHONPATH
> > =====================================
> > *** Building petsc4py ***
> >
>
>
More information about the petsc-dev
mailing list