-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Prebuild Binaries #9
Comments
Yes, that could be possible in general and I use it already for my other public projects. But currently both drone.io and AppVeyor are buggy regarding their C++ environment. For that reason drone.io builds the 64-bit Linux lib (gc 4.8) and AppVeyor the 32-bit Win (Vs2010) lib only. I spent (too) many hours to get the 64-bit VS2010 (or higher) build running at AppVeyor but failed always. Check the build history and the web for hints on that if you like. I assume it is AppVeyor that needs to be blamed here. And drone.io support does not care on such support questions since they did not even answer though they have a large contact button on their site. |
If you can live with the 32-bit Win lib/dll I could find a way, hopefully. |
It would be a another step forward. Absolute links: |
Relative paths do work only: https://ci.appveyor.com/project/tbeu/matio/build/artifacts |
Is this useful for you? |
I have changed to my own 64-bit build (debug/release), but i think for other users it's a nice and simple way to get matio working. |
OK, close it then. |
Any interest in progress being made here? Is there a .dll that can be used for x64 on Windows? |
If you can live with v1.5.12, download matio-1.5.12-win64-vs2015.7z. |
Thanks for the reply. I'll unzip this and check it out tomorrow. If it doesn't work, I plan on building the Visual Studio solution you checked in. |
It would be nice to make a Prebuild lib available.
Maybe you can add .lib/.dll (artifacts) for windows on AppVeyor on the same way as the .pdf/.log here:
https://drone.io/github.com/tbeu/matio/files
The text was updated successfully, but these errors were encountered: