I did the stupid thing and wrote first before researching. My apologies. What
follows is my opinion: Seems like the whole MinGW landscape is a mess when it
comes to 64 bit support (64 bit targets). There is not one main download but a
few different ones from individuals each with its own set of
Are all of these issues resolved for the next HDF5 release? Our project uses
HDF5 and our developers have asked us to support MinGW on Windows. HDF5
building under MinGW was holding us back in the past so I just thought I would
check to see if the issues have been solved?
Thanks
The next release of HDF5 is this fall with the code freeze at the end of
September.
The current code base in svn (including the cmake branch) already works on
Windows 7 and mingw using cmake, with the exception of fortran.
I will work with the autotools experts to review these patches with
I should specify that the problem with generating th e h5pubconf.h file is with
the autotools configure process. CMake works just fine.
Allen
On Thursday, July 19, 2012 08:21:07 AM Allen D Byrne wrote:
The next release of HDF5 is this fall with the code freeze at the end of
September.
The two patches address three issues with the mingw compilation for
non-CMake guys.
To start with, the check for wsock lib would make the patch line:
LIBS=($libs -lwsock32)
obsolete (AC_CHECK_LIB is the right way to do things). I took a shortcut
to get it working right away.
Following that,
Hi forum,
In order to get hdf5 1.8.9 to compile cleanly with no fuzz on mingw,
just patch two files, configure.in and src/Makefile. Then regenerate
scripts with aclocal autoheader libtoolize automake autoconf.
Finally run configure with the option --with-mingw, compile and enjoy.
The
If we added these features to the CMake scripts would that help also? I am more
of a CMake Guy than an autotools guy but I would think adding these flags to
the CMake files for MinGW would allow one to configure HDF5 with CMake on MinGW
(or MSYS).
Thoughts? When is the next release of HDF5
