[petsc-dev] Why --with-dynamic-loading?

[Jed Brown]

Lisandro asks why dynamic loading needs a different initialization procedure

#if !defined(PETSC_USE_DYNAMIC_LIBRARIES)
  ierr = KSPInitializePackage();CHKERRQ(ierr);
#endif

Meanwhile, we use normal shared libraries (--with-dynamic-loading=0)
with plugins (petsc4py dynamically loads PETSc and the petsc-eig plugin
is loaded by PETSc and calls back into SLEPc and PETSc).

What is the use case that --with-dynamic-loading is intended to support?

Can we support that use case without having the configuration option?
-------------- 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-dev/attachments/20130829/c23e805b/attachment.sig>