-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
meson cannot handle full paths in ar (windows) #9730
Comments
Changed it to |
correct fix is probably |
Doesn't seem to be a regression in 0.60.2? Not sure why the title implies it is. |
I think we are running into this in an Azure CI build for a library - the CI environment gives the full path of I can reproduce with Meson 0.61.1 on Windows by creating a file containing just the path to my installation of
and specifying this using
Is there any way to tell Meson explicitly that the |
after fixing #9727 locally.
meson/mesonbuild/compilers/detect.py
Line 295 in a2934ca
will not work if linker is a full path.
meson-native-x64-windows-llvm.log
and thus runs into:
meson/mesonbuild/compilers/detect.py
Lines 331 to 332 in a2934ca
which is wrong. llvm-lib just prints an warning about an unknown option in the detection but that is all (which is why that code path is chosen.).
error:
The text was updated successfully, but these errors were encountered: