CI: Bundle arm64 libraries with Windows multilib package #4846
Conversation
|
FYI @rainers |
kinke
force-pushed
the
ci_winarm64
branch
2 times, most recently
from
f8b4776 to
e30de7e
Compare
|
Nice. I think it's failing because cmake builds and runs test executables during the configuration phase that only run on an ARM64 system. Can this be disabled? |
|
Not sure what the difference is, but for me, cross-compilation works when using instead of |
|
Thx, yeah I guess we might have hit https://developercommunity.visualstudio.com/t/vsdevcmd-creates-invalid-ARM64-build-con/10090339. |
kinke
force-pushed
the
ci_winarm64
branch
3 times, most recently
from
5a0961c to
62e0632
Compare
There was a problem hiding this comment.
I checked the zip in the artifacts, looks good. BTW: I recently also tried the prebuilt libcurl from https://curl.se/windows/, that worked for the phobos unittests, too. I don't remember why we have to compile libcurl ourselves...
Did you test it on x64 or arm64? Great, I don't think they had usable official Windows builds when I last checked, years ago. I don't really remember why we built it ourselves either, but I think one reason was to have a static .lib and the .exp, to enable linking it statically (while still exporting those symbols, so that Phobos can load them from the executable). Looking at the And for 32-bit x86, we might have had to tweak the compile flags to make it work with the MinGW-based libs (disabling I've checked https://vcpkg.io/en/package/curl.html yesterday (wanting to use some prebuilt libcurl too), but looking at the 'Features' tab with all those dependencies made me quickly close the browser tab again... ;) |
|
Sorry for the delay. I tested libcurl successfully on arm64. I guess you are right about the static library build, maybe they even had mingw runtime dependencies back then. |
No description provided.