-
Notifications
You must be signed in to change notification settings - Fork 464
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
Failed to build libwdi dll #238
Comments
My configuration is not the same as default but it should not matter.
|
Same for x64 only build.
|
I just did the build libwdi on a week ago on 25 Oct 2021 with the following commits. |
Just upgraded VS2019 to the latest version and it is now okay.
|
New version VS2019 16.11.5. I was using 16.11.2 previously. |
FYI libusb-win32 1.2.7.2 is not a formal release but a signed snapshot release, it may not work under Windows 7. It works under Windows 10 and Windows 11. |
Okay. Just FYI, as long as I don't see an official libusb-win32 release in https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/, I'm not going to upgrade the one I use in Zadig. Also, if you ever have doubts if the library compilation is broken or if it's your environment, just check for failures in https://github.com/pbatard/libwdi/actions. For every commit, a build is issued for all of the VS2019 and MinGW targets, so unless you see a failure there, it's probably your environment. |
Yes that libusb-1.2.7.2 snapshot release is not a formal release. Therefore it is correct not to include it in Zadig official release. |
As for the VS2019, it is rather strange but anyway it is fixed after I update my VS2019 community edition installation. So it is all good now. |
For those who want to try out libusb0.sys 1.2.7.2 snapshot release, you can try my build of Zadig here. Build with VS2019. Tested with Windows 10 and 11. Not so sure if it works under Windows 7/8/8.1. It will not work under Windows XP. Unlikely it will work under Windows Vista either.
|
Hello, I am also getting the linker error mentioned above related to the "NtQuerySystemInformation" unresolved symbol. It only occurs when I build the dll, but not the static lib. I'm building with VS 2022, most recent available update (17.0.5) with platform toolset v143. Is there any known fix for this error which involves a change to configuration, or do I need to roll back to VS 2019 or toolset v142? |
@njk42, I am not seeing any issue with VS2022 compilation on the most recent update (2f4186c, using toolset v143). The GitHub Actions build of the VS2022 updated project files also show no issue. Therefore, we have to conclude that whatever issue you are facing comes from your environment and not the project, as the project does build fine with VS2022. |
@njk42 Try to upgrade your VS2022 installation. The current libwdi git head is targeting VS2022 and it works. I just installed VS2022 and there is no issue building libwdi git head.
|
@mcuee I don't think the dll is getting included as part of the Solution build. From your output above:
The default solution settings have the dll unchecked from the build for both x32 and x64. It's when I try to explicitly build the dll project that I get the linker error regarding NtQuerySystemInformation. |
@njk42 You are right. I can reproduce the issue when building the dll.
|
Looking back my original report and it was also because of the dll building. |
Just try to rebuild 1.4.1 release with the just updated VS2019 and I can see the issue with the DLL build as well.
|
Yes this is now fixed.
|
It is a bit strange that I can not build latest git (libwdi 1.4.1) using VS2019
The text was updated successfully, but these errors were encountered: