https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #63 from Jaroslav Skarvada <jskar...@redhat.com> --- (In reply to Jaroslav Skarvada from comment #62) > Regarding the libwdi, I could try to get it into the MXE, but it seems it > needs bundling of the libusb windriver which I currently don't know whether > it's possible from the MXE, but I will check it. Then it should be matter of > few libwdi API calls (which could be copied from the examples section of the > documentation). I think the camera dialog will have to be patched and the > install button will have to be added. Unfortunately, the libwdi API doesn't > support uninstallation of the drivers, thus the driver will have to be > manually uninstalled by users (if required), but it shouldn't be blocker. The libwdi requires the libusb-win32 which provides the 'sys' drivers. Unfortunately, I wasn't able to compile the libusb-win32 with the recent mingw. It seems it uses obsoleted winddk (for xp/vista). Fixing it to compile with the recent mingw will require porting it to the recent wdk (https://github.com/mcuee/libusb-win32/issues/30) which is currently out of my scope. You could build the libwdi out-of-the mxe tree and bundle the libusb-win32 sys driver as a binary blob (i.e. download the compiled binary sys driver from the internet). Maybe this is inefficient overhead. I think it could work fine with the original MS winusb driver. Just the INF file unbinding the native PTP driver not to take over could be enough. This is what the Zadig also supports, but unfortunately for the libwdi you will have to compile with the `--with-wdkdir="<dir>"` to embed the WDK redistributable components files. This will probably require downloading the WDK, which is something that cannot be done in the mxe. But again you could probably compile the libwdi out-of-the mxe tree and bundle the WDK redistributable components there (but I don't know what the MS license allows). -- You are receiving this mail because: You are watching all bug changes.
