Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread Kirk, Benjamin (JSC-EG311)
On Apr 1, 2013, at 11:32 AM, Cody Permann wrote: > Hmm - I like that idea! Should we make it an option since 99% of our users > don't need it? Definitely, also since it'll be the first code to actually use the Fortran compiler inside our build system… We should default it to off, and also ma

Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread Cody Permann
Hmm - I like that idea! Should we make it an option since 99% of our users don't need it? Cody On Mon, Apr 1, 2013 at 10:29 AM, Kirk, Benjamin (JSC-EG311) < benjamin.kir...@nasa.gov> wrote: > On Apr 1, 2013, at 11:20 AM, John Peterson wrote: > > > I think there is probably a sanctioned manner

Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread Kirk, Benjamin (JSC-EG311)
On Apr 1, 2013, at 11:20 AM, John Peterson wrote: > I think there is probably a sanctioned manner for getting the Exodus Fortran > bindings compiled along with Exodus itself. > > Our first attempt, which was just copying exo_jack.c over from the forbind > directory, is just not the right appro

Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread John Peterson
On Mon, Apr 1, 2013 at 10:10 AM, Kirk, Benjamin (JSC-EG311) < benjamin.kir...@nasa.gov> wrote: > On Apr 1, 2013, at 9:53 AM, Cody Permann 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 >

Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread Cody Permann
OK thanks, We are in the process of pushing a new version of libMesh to our users right now so this won't make it in there anyway and we won't update again for ~3 weeks. For now, I'll have our one user copy the file to his own contrib directory. Perhaps he isn't using the Fortran bindings in the

Re: [Libmesh-devel] exodusII_int.h

2013-04-01 Thread Kirk, Benjamin (JSC-EG311)
On Apr 1, 2013, at 9:53 AM, Cody Permann 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.

[Libmesh-devel] exodusII_int.h

2013-04-01 Thread Cody Permann
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? Thanks, Cody -