On Nov 19, 2012, at 4:22 PM, "Kirk, Benjamin (JSC-EG311)" <benjamin.kir...@nasa.gov> wrote:
> On Nov 19, 2012, at 4:12 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > >> On a barely related topic: >> >> What's with the need for specific LIBMESH_ENABLE_FPARSER testing in >> example Makefiles? Shouldn't that be part of the general >> LIBMESH_INCLUDE construction? > > Before doing make install, fparser's header files are buried in > contrib/fparser. After install we put fparser.hh in > $prefix/install/libmesh/fparser.hh > > In retrospect, now that we symlink everything into include/libmesh it would > be better to put fparser.hh there as well. I'll fix that, probably tomorrow. But to expound, you'll notice not all the contrib/... headers get installed. Almost none of them are needed by a user application, but rather we need them to build the library. fparser is a special case, and I think I add exodus/nemesis too for the MOOSE guys, but installing the laspack header files under 'include/libmesh/...' seemed a step too far. Likewise with metis, parmetis, etc… -Ben ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
