-
Notifications
You must be signed in to change notification settings - Fork 95
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
Windows build fails to link #53
Comments
Oh, Windows, Windows. I don't recognise this error - I guess you are not using Windows yourself either, but does this CI flow suggest any obvious way to reproduce the flow locally? There is a RB Windows CI build, and it is currently succeeding (example log here). It tests both Meson and "old-school" Visual Studio projects, using VS2019. (Also of course I built and packaged the 2.0.1 command-line utility this morning on Windows with VS2019, so it clearly worked for me as well!) The error looks a bit like the static archiver not recognising the options it's given - perhaps an unexpected archive tool in path, or something has detected it wrongly? The argument quoted ( |
Yeah there are no matches for |
I downloaded the archive of all the logs from vcpkg's CI and the only time the string
|
The equivalent link command in my local build appears to be
which is quite different. I configured with |
|
I suppose the most obvious difference is the version of Meson, but the successful runs are using both older (0.55, mine locally) and newer (0.60 on AppVeyor) versions of Meson than the failing one (0.58) which would seem to make that a little less likely a cause. |
Anything suggestive in those |
|
I am not passing any options to Meson, only using vcpkg's standard Meson macro. |
It looks as if Meson tries to determine whether a static linker is the Visual Studio one by calling it with a (edit) Is there a Meson config log file? Typically |
Mm, nothing very useful there. My hypothesis is that because |
Another vcpkg package using Meson also ran into this recently, unfortunately with no solution figured out: microsoft/vcpkg#22196 (comment) |
Yep, that seems to be right. I create a native file specifying nothing except
Then I configure a new build directory and
I'll check using the latest version of Meson (even the newer one in the AppVeyor CI is not the very latest). |
Still a problem with Meson 0.61.1. |
This looks very like mesonbuild/meson#9730 |
Oof... thanks for looking into it. |
Discovered on vcpkg CI
Meson output:
The text was updated successfully, but these errors were encountered: