On Thu, Sep 13, 2012 at 11:34 AM, Kirk, Benjamin (JSC-EG311) <email@example.com>
better because I still want sudirectories to organize the header files.
On 9/13/12 11:19 AM, "John Peterson" <firstname.lastname@example.org
>> #include "libmesh/base/dof_map.h"
> Better because more unique? Feels a little "boost"y to me, but I
> guess I could get used to it.
would be fine but would require we create a libmesh directory inside each of
our current subdirectories, and it is the only thing in there. So we'd have
include/base/* -> include/base/libmesh/*
include/enums/* -> include/enums/libmesh/*
You shouldn't need to do this in the source. We could retain the current directory infrastructure in the source and use the build system to install everything in $LIBMESH_INSTALL/include/libmesh/
I like this because you can still have uniqueness wrt to libmesh headers but without creating a large directory hierarchy. Of course, this is predicated that one will be buidling apps against the install and not the source.