>> So --with-parmetis=/foo >> >> and then in David's case he'd precompile parmetis and point petsc and >> libmesh to the same one? > > Right - unless the default PETSc install already leaves parmetis > headers and libraries someplace accessible, in which case only libMesh > would need non-default options.
I'll veto this one out of principle - it's enough work maintaining compatibility with multiple PETSc APIs - no way can we support linking to wherever they put their external library builds across multiple versions! We can however support --with-parmetis=... and it can be up to David to know where PETSc puts its builds and adjust the libmesh configuration accordingly. What I envision is a --with-parmetis= and also a --with-parmetis-include, --with-parmetis-lib which can be used to configure with various levels of granularity as needed. I'll see what I can do... -Ben ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
