On Apr 1, 2013, at 9:53 AM, Cody Permann <firstname.lastname@example.org> wrote:Same reason we don't install e.g. fparser/extrasrc/fpaux.h
> We have a user that is using exo_jack.c (part of the FORTRAN bindings for exodus) but we are missing a header file in the installed version of libmesh. I haven't really dug around but is there a reason that we aren't adding exodusII_int.h to the installed include directory?
The exodusII_int.h file is not considered part of the external ExodusII API, so we don't install it. In general we try not to 'pretend' to be any of the contributed packages - if we can compile libmesh.so from them and then not include them at all in the installation, that would be ideal. This is how we use sfcurves, for example. None of the libMesh header files require it, so we don't install their API. We just compile and link to it internally.
That said, the only reason we install exodusII.h at all now is because we make an exception for you guys, and I'd be OK installing their internal header file if you really need it!