-
Notifications
You must be signed in to change notification settings - Fork 47
AppVeyor builds failing #295
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
Comments
I don't know how to fix it, so I left it alone. I would appreciate it if someone could fix it. |
The only way that someone can help fix it would be if the AppVeyor config was included, at least partially, as a file in the repo. I think you currently have it setup so that the entire configuration lives in AppVeyor which is the default behavior. |
Here is a link to the docs for I think there might be a way to export your current configuration as one of these YML files so it can just be committed. Otherwise, it would need to be built up with your specific needs for automatic builds. |
Some settings were fixed.
ntddcdrm.h is Windows Driver Kit file, there is not in the repository. How do I build files that is not in the repository? |
According to their docs, the only versions of the WDK that are installed in the image by default are WDK 8 (available with Visual Studio 2013) and WDK 10 (available with Visual Studio 2015, 2017, 2019). I forgot about the dependence on the older WDK, specifically WDK 7, that's needed for DiscImageCreator on Windows. It seems like the only way to get around this would either to update to WDK 8 (which officially supports only Windows 7 and above) or find another auto-building solution. I can look into if Jenkins or GitHub Actions can support this, though it's starting to get old enough that it may not. |
Okay, unfortunately Jenkins relies entirely on what you have on your machine and GitHub Actions only goes back to Windows Server 2019 and they only include WDK 10 versions from that onward. Automatic Windows builds may not work properly on the common platforms due to the atypical combination of build requirements. |
Describe the bug
Currently, AppVeyor immediately fails to build the project because there are two solution files that are included in the repo. To fix this, I think the only thing that needs to happen is that either the Windows or Linux solution file has to have the path provided as the default and it should behave correctly.
The text was updated successfully, but these errors were encountered: