[petsc-dev] building PETSc plugins separately

[Barry Smith]

On Nov 23, 2013, at 5:35 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> 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
> installed.

   Yes, we would need to modify our current makefiles