Hm, do you have any idea how to fix this?
No, I'm not a developer. Not sure if it is expected behavior in meson, however.
I'm not at home right now, but can you try
CC=winegcc CXX=wineg++ [your meson command]
and see if that fixes it?
This is weird though, since dxvk_compiler should be the compiler that is used to compile the entire project, and that is wineg++ as defined in the crossfile. Anyway, looks like this might need some digging.
@Joshua-Ashton Yes, it helps. Would it break something?
@Joshua-Ashton Yes, it helps. Would it break something?
By saying it helps, do you mean it fixed the issue? or..
I mean it compiles. Didn't try to run it.
I get these these warnings, although it still compiles:
WARNING: Env var CC seems to point to the cross compiler.
This is probably wrong, it should always point to the native compiler.
WARNING: Env var CXX seems to point to the cross compiler.
This is probably wrong, it should always point to the native compiler.
For some reason meson decided to run these tests with the native compiler for some for you it seems?
If this is an intended change in Meson, and not something else, it is rather misguided and doesn't really make much sense as its running with dxvk_compiler :/
This may be the root cause https://github.com/mesonbuild/meson/issues/5102
@dhewg Thanks for digging into this, I'm still on 0.49 and frankly have better things to do than worry about build issues, so this is really appreciated.
Hehe, same here. I just ran into the same issue on https://github.com/iXit/wine-nine-standalone and downgraded too ;)
Bug report here:
0.50.1 is out, which should fix this issue
I can confirm that 0.50.1 fixes the issue.
Nice, closing then.
Nothing extracted yet.
With meson 0.50, winelib check fails.
Corresponding
meson-log.txtpart:With meson 0.48 dxvk builds fine. I guess the problem is that meson uses native compiler instead of cross-compiler to run the compiler test (
dxvk_compiler.compiles(code, name: 'winelib check')).