As a workaround, I created a symlink in $HOME/.local/bin and it helped:
ln -s /usr/bin/x86_64-w64-mingw32-widl $HOME/.local/bin/widl
In that case also make sure that $HOME/.local/bin is in your $PATH.
I see there is also this from wine64-tools: /usr/bin/widl-stable.
Hm, that's actually a newer one. So doing this also helped:
ln -s /usr/bin/widl-stable $HOME/.local/bin/widl
Hm, that's actually a newer one. So doing this also helped:
ln -s /usr/bin/widl-stable $HOME/.local/bin/widl
Why is Debian renaming the widl binary like this?
Not sure, but my suspicion is that may be they wanted to differentiate wine64-tools as "stable" and "development" variants?
That's what I see in it:
...
/usr/bin/widl-stable
/usr/bin/winebuild-stable
/usr/bin/winecpp-stable
/usr/bin/winedump-stable
/usr/bin/wineg++-stable
/usr/bin/winemaker-stable
/usr/bin/wmc-stable
/usr/bin/wrc-stable
...
May be one option would be to check for widl-stable in addition or to mention in documentation that symlink would be needed on Debian.
May be one option would be to check for widl-stable in addition or to mention in documentation that symlink would be needed on Debian.
The main problem is that Meson broke this (check for mingw-tools, then fallback) and it's not obvious to me how to make it optional.
find_program can take required : false which we could technically abuse to allow multiple binary names, but things having random names across different distros really isn't helpful.
After a few weeks of not updating vkd3d-proton for Lutris, I tried compiling it today but it seems that a similar issue is present with Fedora 37 as well.
All dependencies are installed (as I was compiling fine earlier), running Meson v1.0.0, WINE v8.2 and mingw-w64-tools v10.0.0 from Fedora's repo.
When searching for 'widl', my system finds the following:
/usr/bin/i686-w64-mingw32-widl
/usr/bin/x86_64-w64-mingw32-widl
/usr/bin/x86_64-w64-mingw32ucrt-widl
I did exclude a few entries from the list above, specifically for WINE runners in Lutris, Bottles and Heroic (which include 'widl' in their respective 'bin' directories) but I didn't notice one for the system-wide installed version of WINE from Fedora's repo, aside from what was listed above.
Not sure if this makes a difference (although, as mentioned, it was compiling fine a few weeks ago on the same system).
Update: So after re-adding the entries in build-win32.txt and build-win64.txt, that were removed in 2ec6c90, it compiles fine.
https://github.com/HansKristian-Work/vkd3d-proton/pull/1470 attempts to fix this. Seems to work here at least.
Commit 2ec6c90ab6676e328883651783e3822579234386 broke building vkd3d-proton on Debian (testing).
I think the only source of widl there is
mingw-w64-toolspackage which provides:So there is no simply
widlbinary.