You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per #197 and also #129, it seems we can only avoid conflicts between HDF5 versions by using exactly the same version as Matlab. We therefore need to check that if we build with Matlab, we download the same HDF5 version and build with that (as we cannot use Matlab's HDF5 libraries).
The code here illustrates how to call matlab (will need to use $(Matlab_MAIN_PROGRAM)). Here is an example for parsing the output (but the parsing there is far too complicated for what we need of course).
The text was updated successfully, but these errors were encountered:
- use version HDF5 1.8.12 on Windows if Matlab is being built (see #208). At the moment the version is hard-wired. However, this likely introduced a conflict with Python as it usually uses a more recent version of HDF5 (certainly the Anaconda version does)
- add a patch for HDF5 1.8.12 such that it compiles post VS 2013.
- introduce a HDF5_DOWNLOAD_VERSION variable
- introduce a HDF5_CMAKE_ARGS variable for use in the cmake files that depend on HDF5
This now works fine on Windows as far as I see. On Windows, we will need to have 2 separate builds for MATLAB or Python support unfortunately.
As per #197 and also #129, it seems we can only avoid conflicts between HDF5 versions by using exactly the same version as Matlab. We therefore need to check that if we build with Matlab, we download the same HDF5 version and build with that (as we cannot use Matlab's HDF5 libraries).
Info from Mathworks
The code here illustrates how to call matlab (will need to use
$(Matlab_MAIN_PROGRAM)
). Here is an example for parsing the output (but the parsing there is far too complicated for what we need of course).The text was updated successfully, but these errors were encountered: