On Apr 1, 2013, at 9:53 AM, Cody Permann <codyperm...@gmail.com> wrote:
> 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? Same reason we don't install e.g. fparser/extrasrc/fpaux.h 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! >From exodusII_int.h: /***************************************************************************** * * exodusII_int.h - ExodusII header file for internal Exodus call use only * */ ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
