[petsc-dev] petsc makefiles

[Jed Brown]

Blaise A Bourdin <bourdin at lsu.edu> writes:

> Hi,
>
> Is there a way in petsc makefiles to figure out how to link a shared / dynamic library
> i.e. if I want to know how to do 
> 	$CC -shared *.o lib.so
> vs.
> 	$CC -dynamiclib *.o lib.dylib
> what variable gives me the extension .so vs .dylib and the linker option -shared vs -dynamiclib

See SL_LINKER_FUNCTION and SL_LINKER_SUFFIX, e.g., as used from gmakefile.

> How about doing the same thing in BuildSystem (I need to build a shared library for exodus)?

Isn't the Exodus build system capable of that?

> Also, is there a way to know the family of compiler I am using (gnu vs intel vs something else)?
> The long line fortran compiler options for fortran and ifort are of course different, and the default behavior opposite…

That option goes into FC_FLAGS.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170720/5da5bbde/attachment.sig>