-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom command execution failed when building x86-windows #636
Comments
We just made some changes in that CMake code for the ninja build system. Please try the latest development code from either develop or the 1_12 branch. |
@byrnHDF When we publish the new method to a release? |
If the question is when are our next releases; |
I will try 1.12.1 later. |
I read the code of 1.12.1, |
I looked at that issue and the problem was our cmake code and ninja had issues. Which I believe we fixed in time for 1.12.1 and is now in all our development code. |
I will confirm that later. |
Trying to build current "develop" source with MinGW-w64 in MSYS2 shell I get:
|
This will be addressed by PR #1089 |
@JackBoosY, @byrnHDF - can this be closed now? FWIW, H5detect and H5make_libsettings have been removed from the library in develop and the 1.14.2 release will include that change. This makes the 'stamp' hack irrelevant. You might want to give develop a try to see how that works, as well. |
For me current develop builds for x86_64-w64-mingw32 and i686-w64-mingw32 succeed under MSYS2 shell with CMake+Ninja on Windows 11. |
Are there any patches or hacks that you need to add that are missing in the library? There are other issues relating to MinGW that I'd like to get fixed. See #2408 and #3091, for example. |
I built the unchanged develop sources. No additional patches. |
I guess this issue was fixed. |
Hi guys,
I'm vcpkg maintainer.
A few months ago we received an issue about building hdf5 (microsoft/vcpkg#16203), and users reported to us that there was an error when building hdf5::x86-windows using vcpkg:
After a period of investigation, I think this is caused by the use of
add_custom_command
to call scripts or commands, but it did not report any error messages.And I can't reproduce it on my local machine.
Can anyone help us?
Thanks.
Edit: This should not related to permissions.
The text was updated successfully, but these errors were encountered: