On Thu, 13 Sep 2012, Derek Gaston wrote: > Another option is to put a "libmesh" symlink underneath include that > points to include... so #include "libmesh/base" will work fine... > then no source files need to be moved... and you don't have to > traverse the extra directory when you're working in libMesh...
Hmm... that's a pretty slick way to handle in-place builds. But with a "make install" target I think we'd want to clean up our current "dozen subdirectories under $prefix/include" with a single $prefix/include/libmesh top level include directory anyway. --- Roy ------------------------------------------------------------------------------ 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
