On Thu, Jan 31, 2013 at 7:34 PM, Matthew Knepley <knepley at gmail.com> wrote:
> On Thu, Jan 31, 2013 at 7:25 PM, Geoffrey Irving <irving at naml.us> wrote: > >> We have an scons build system linking against PETSc, and it would be >> nice to have an automatic way of determining the list of libraries >> that a statically linked, installed version of PETSc wants (e.g., the >> MacPorts installed version). What's a good way to do such a thing >> from *outside* the PETSc build system? >> > > It depends on how much work you want to do. For at least two years I think, > our default had been -lpetsc. I would just do this. > Satish is right, use 'make getlinklibs'. However, if you don't have to waste time on a life or family, you may want to consider getting the info straight from the configure. You can load up the Python module from from $PETSC_ARCH/conf/RDict.db and pull out all these things. There is an example in configVars.py. Matt > Matt > > >> Thanks, >> Geoffrey >> > > > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130131/b3e08ffa/attachment.html>
