Interestingly enough, NOT setting the "export WIDL='/usr/lib/wine/widl'" in the "rules" file for deb build, makes dpkg-buildpackage build fine locally. If i do not set that export, Launchpad does not find WIDL at all tho.
Setting this export line make the configure script fail on the version extraction for some reason. Dunno how all the configure lines involved in finding this version actually work tbh, so i am rather clueless how to solve this.
Just doing: widl -V | sed -E '/version/{s/.* version (.*)/\1/;q;}' outputs "4.0" for Disco, but all the "ax_compare_version_A/B"+++ stuff, i dunno how to manually test.
In retrospect, building vkd3d for bionic/cosmic for WineHQ is probably not an option, cos vkd3d needs libvulkan > 1.1.84, but Bionic only provides libvulkan-1.1.70, and Cosmic libvulkan-1.1.82.... and providing backported packages on WineHQ repo was not something anyone was too happy doing.
Sveinar Søpler
----- Original Message ----- From: "Sveinar Søpler" cybermax@dexter.no To: "wine-devel" wine-devel@winehq.org Sent: Saturday, April 13, 2019 9:31:09 PM Subject: Re: [PATCH v2 vkd3d 1/4] build: Drop hack for stripping RPC includes from widl-generated headers.
Hmm. I guess its the fakeroot environment that does something weird when building package with dpkg-buildpackage, cos running regular "configure" does not show this error. config.log using dpkg-buildpackage reads: -- configure:4562: result: '/usr/lib/wine/widl' configure:4572: checking checking whether widl version >= 3.20 configure:4610: result: no () -- Outside of the fakeroot env, widl is a symlink from /usr/bin/widl -> /etc/alternatives/widl -> /usr/bin/widl-stable -> ../lib/wine/widl I guess some of this symlinkery fails in the fakeroot, even tho configure finds the actual binary in /usr/lib/wine/widl. Ill dig a bit and see what i can figure out.
I maintain a Launchpad PPA for vkd3d packages, and i must say it's a shame vkd3d cant be built for Ubuntu bionic/cosmic on launchpad anymore.
I talked a wee bit with DiMesio about building vkd3d for wine-devel on the OBS, but did not come to an agreement with her about placements of libraries. But since vkd3d can't be built on launchpad anymore i might look more into using OBS for bionic/cosmic packages perhaps. If it is of any interest, i'm willing to discuss it some more.
I would however say that if it should become a "winehq provided package", it should be possible to use it for something. As of now, release 1.1 does not work with anything and should probably not be used for this. Best option would be to have the two "hack patches" needed for WoW to work implemented + do a release 1.2 with that. Why? Yeah, cos if the packages are actually included with wine-devel it would be nice to have it support playing WoW :)
Sveinar Søpler
----- Original Message ----- From: "joseph kucia" joseph.kucia@gmail.com To: "Sveinar Søpler" cybermax@dexter.no Cc: "wine-devel" wine-devel@winehq.org Sent: Saturday, April 13, 2019 11:13:52 AM Subject: Re: [PATCH v2 vkd3d 1/4] build: Drop hack for stripping RPC includes from widl-generated headers.
On Fri, Apr 12, 2019 at 11:12 PM Sveinar Søpler cybermax@dexter.no wrote:
There is some strangeness with the configure check of widl i think?
checking checking whether widl version >= 3.20... ./configure: line 4574: '/usr/lib/wine/widl': No such file or directory no () configure: WARNING: widl is required to build header files. -- :$ widl -V
Wine IDL Compiler version 4.0 Copyright 2002 Ove Kaaven --
Do you have the WIDL environment variable set? Do you set it when running configure? config.log should be helpful to diagnose your problem.
Is there some new function in widl 3.20 that would fail this with widl 3.0? (Due to the fact that Bionic and Cosmic only has wine-3.0.x available from default repo)
widl 3.20 or newer is required. The configure test checks the widl version.