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

Jed Brown jedbrown at mcs.anl.gov
Thu Aug 29 09:41:25 CDT 2013

Matthew Knepley <knepley at gmail.com> writes:

> On Thu, Aug 29, 2013 at 9:30 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>> Matthew Knepley <knepley at gmail.com> writes:
>> > Dynamic libraries give us a hook when we load them, but we do not have
>> > that statically. I could not think of another way to do it.
>> I understand that dynamic libraries allow you to do so, but what does
>> that buy you?
> You do all the logging initialization.

That happens in PetscInitialize and in XXInitializePackage, the same as
for static libraries or normal shared libraries.  What is the practical
benefit of having PetscDLLibraryRegister_petscksp call
KSPInitializePackage when using dynamic loading?  Specifically, what use
case needs this?
-------------- 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/e0c85de3/attachment.sig>

More information about the petsc-dev mailing list