Windows 11 (arm64) - PR Artifacts - Vulkan headers - CPack workaround #1866
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NSIS replaced by INNO Setup Workflow adapted, as DX9 Grabber is no longer included
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
GitHub: Windows 11 (arm64) has been added to the Qt6 workflow build
Fix: For Windows, pull request artifacts are now built with RelWithDebInfo (Windows PR Build doesnt start webui and links to ucrtbased.dll #1865 )
The need for Vulkan headers (Qt6) was removed from the workflow and the Qt6 warning message was suppressed using a CMake inferface target
The CPack workaround for macOS 13 (GitHub Actions) has been moved to the hdiutilwrap.sh script
Disable DirectX grabber per default
Replaced exceptions by signaling errors in main program
Add SignalHandling to Windows
Bugfix
Feature
Code style update
Refactor
Docs
Build-related changes
Other, please describe:
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Fixes: #1865
Fixes: #1582