[petsc-dev] PETSc-3.4 PR open at https://github.com/Homebrew/homebrew-science/pull/343

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:

>   This whole prefix/include and prefix/lib seems rather silly and
>   archaic; who uses it but the gnu/linux people ?  For example on
>   MacOS the PETSc install location is
>   /Library/Frameworks/PETSc.framework, on Windows they must have some
>   convention but it sure as hell doesn't use include and lib.

The MacOS "framework" thing provides a way to associate headers with
libraries.  It's debatable whether it's better or worse, but it
certainly broke compatibility for lots of things and it binds linkers
and compilers more closely.

>    Why does the linux world (which is tiny) cling to this archaic
>    model?

It has always worked and is compatible.  If you assume shared libraries
(which Apple can do because they control the ecosystem) then -lpetsc
is all you need.  Why do you want to type "-framework PETSc" instead of
"-lpetsc"?
-------------- 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/20131012/79dc73b4/attachment.sig>