> 3.1.x PETSc is all in one library? 3.1 introduced a configure option --with-single-library. This is the default because it simplifies linking, but we still support keeping the libraries separate (--with-single-library=0). I think most of the PETSc developers have them separate just because it keeps us honest about module decoupling, and presumably there are some users that do this as well. If you want to support --with-single-library=0, then you can check PETSC_USE_SINGLE_LIBRARY (will not be defined in this case) and link as before, but with -lpetscsys for the core stuff.
Jed Note that an alternative to all the version checking is to snarf the output of "make getlinklibs" or the value of PETSC_TS_LIB (or PETSC_SNES_LIB since you don't currently use TS) which is guaranteed to work with all versions of PETSc, in all configurations, including with static libs and arbitrary third-party dependencies. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
