Hi,
Noting the MinGW64(4.8) style of building: just tried the
cmake(2.8.11.1) build approach for hdf5(1.8.11). Some gliches and I do
appreciate the effort of build tools such as cmake.
I do try every now and then but fall back to building hdf5 and hdf5_hl
by selecting the sources in NetBeans projects and after
blending/updating a few config headers build it with the make files
generated from NetBeans
I suspect most developers(including me) since we're all busy don't give
feed back often enough. We get something working and don't have the
time to share experience.
First thing with cmake build hit was the executable looking for a good
make. make's on windows has differences and I have a gmake of recent
enough that works so I pointed it to it. Get further then turn on
parallel and keep filling paths to openmpi libraries and cmake rejects
for a bit and then finally the right combination is hit and it is satisfied.
Configure done.
Generate done.
gmake goes at building H5detect.exe and soon hit undefined reference to
'__imp_gethostname'
Now as a developer I know my end code won't depend on this H5detect.exe
so I at this point just go back to building with my handy NetBeans make
scripts which build hdf5 with openmpi readily and I'm in business with
hdf5 1.8.11 upgrade. Able to build window's dll's that aren't dependent
on being under cygwin; they are windows dll's
Of course I take care of a couple of H5_HAVE_WIN32_API preprocessor
choices since mingw64 is closer to the !H5_HAVE_WIN32_API case. The
distinction of WIN32 is for me more a distinction of using Microsoft
tool chain. Instead my preference is portable compiler such as g++
4.8. The portion I had to break/comment out this time until I need it
is the H5PL plugin code
On 06/10/2013 01:28 PM, Allen Byrne wrote:
One clarification - The CRT option IS a compiler flag, it's just
simpler to think of it as a link issue.
Allen
On Monday, June 10, 2013 08:56:14 AM Allen Byrne wrote:
It seems to me that the discussions are not being specific enough with
which build/CRT configuration is discussed.
In my opinion there are two CRT issues and two build issues:
1: Linking with static CRT(/MT) and linking with dynamic CRT(/MD).
2: Building static libraries and building dynamic libraries.
Therefore there a four configurations of which we supply the cmake
code and binaries for the two build configurations with just the
dynamic CRT.
Allen
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
