[petsc-dev] building PETSc plugins separately

Jed Brown jedbrown at mcs.anl.gov
Sat Nov 23 17:35:50 CST 2013

Barry Smith <bsmith at mcs.anl.gov> writes:
>> It's messier for static libraries because the user needs to link them
>> explicitly.  If we create a petsc-config program (similar to pkg-config,
>> but I think we need to execute our code), it could walk through the
>> designated plugin paths to construct a suitable link line that would
>> include all the plugins.
>    Yupe
>    Or if users used our makefile :-)

Using our makefile is not enough unless the makefile can use $(wildcard)
or $(shell) to become aware of the plugins once they have been
-------------- 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/20131123/bed23d73/attachment.sig>

More information about the petsc-dev mailing list