>> 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...
Also, WRT: > How do we need symlinks, again? > > Move e.g. include/base/ to include/libmesh/base/ > Change the current include path options to match. > Add another include path of "-I$LIBMESH_DIR/include". > And add a configure option to remove the current-style paths. > Done. Both these options work fine, and are an equivalent way to go. The only downside is that the user needs to know the subdirectory the header lives in, and change the path if we move it. On the other hand, an alternative option is to create include/libmesh and then link all the headers in there. So, any preferences? #include "libmesh/dof_map.h" or #include "libmesh/base/dof_map.h" -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
