Hi Andrew, Am 16.11.12 23:32, schrieb Andrew Collette: > Hi Mike, > >> I tend to use MinGW32 (http://www.mingw.org/) to compile C extension for >> Python on Windows. I know from experience it can compile and link against >> VS2003 and VS2008 for different Python versions. I remember doing it at least >> for 2.5, 2.6 and 2.7 using source code distributions of packages with pip or >> setuptools/distribute. MinGW32 can figure out how to link against the right >> library version. > > Thanks for the info! But in this case I think we have a slightly > different problem. The generally available Python builds (from > Python.org and distributors) are VS2008, and if HDF5 itself isn't > built with VS2008, we have two separate versions of malloc and free > from the two separate msvcrt*.dll runtimes. At the end of the day > what we really need is *HDF5* built with the 2008 runtime dll. This > is why dropping VS2008 support in HDF5 is concerning.
I see your point. Your are still at the HDF5 level not at the Python extension level yet. But maybe you can still look at how MinGW32 compiles Python extensions. It links against the right VS version run time libraries. So using MinGW32 to compile HDF5 itself and set the lib and include paths to VS2008 might work. So dropping VS2008 support would mean no VS project file. But a make (or cmake) file that takes care of all the compiler flags and linking issues to build against VS2008 run time libraries might work. Does it make sense or am I am making things too simple here? Mike _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
