[petsc-users] ExodusII

[Jed Brown]

Baros Vladimir <vbaros at hsr.ch> writes:

> Necessary header files, can be found here:
> https://code.google.com/p/msinttypes/
>
> It contains necessary inttypes.h and stdint.h headers
> I successfully used them to build exodus lib with Visual Studio.
>
> Can anyone enable the support for exodus in Windows?

As I said in my reply to Pedro, stdint.h is system functionality that is
none of PETSc's business to be installing.  PETSc could add tests for
those headers and if so, attempt to build Exodus.II.  But upstream
really has to at least claim to support it.  (We are not Exodus.II
developers.  The --download-* functionality in PETSc configure is
supposed to be a convenience only, but it generates a disproportionate
support workload.  Attempting to support a configuration that upstream
does not support and that is not used by any active PETSc developer is
inviting increased support workload and a poor user experience.  You're
always welcome to install Exodus.II or any other library yourself.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20140530/6fafb5ff/attachment.pgp>