Re: [petsc-dev] petsc makefiles

2017-07-20 Thread Jed Brown
Blaise A Bourdin writes: >> Isn't the Exodus build system capable of that? > > My understanding is that we use a repackaged version of exodus 5.24 with a > crappy makefile. More recent version (6.0+) use cmake and automatically build > the shared library. I seem to have issues with the latest re

Re: [petsc-dev] petsc makefiles

2017-07-20 Thread Blaise A Bourdin
> On Jul 20, 2017, at 6:49 PM, Jed Brown wrote: > > Blaise A Bourdin 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.dyl

Re: [petsc-dev] petsc makefiles

2017-07-20 Thread Jed Brown
Blaise A Bourdin 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

[petsc-dev] petsc makefiles

2017-07-20 Thread Blaise A Bourdin
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 H