On 9/13/12 11:39 AM, "Paul T. Bauman" <ptbau...@gmail.com> wrote:
> 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/ Well, that assumes we have a 'make install' - which only exists in automake now... But even then when we are building the library internally to the build system and the header files have not been redistributed by an install rule we'd need to be able to find them, which I think would require a move as described, right? Enough of us develop libMesh and apps I'd hate to have to mentally say #include "dof_map.h" when editing libmesh source files but have to switch to #include "libmesh/dof_map.h" when using the external API... -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
