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
build: disable Vulkan validation layers #17985
Conversation
8626f19
to
5f4c79a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it still makes sense to disable vulkan code if its not being used. enable_vulkan=false
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree with @deepak1556, I think we should revert the change and leave enable_vulkan at its default as it doesn't cost us much to leave it enabled.
whats the benefit of this ? |
It keeps us closer to Chromium's configuration. I'd rather ask, what's the benefit of disabling it? :) |
Cool, I am not super tied to my argument, but just that what we are doing is just disabling a subset argument to achieve the main purpose, while the main gateway for vulkan in the codebase is |
If we're going to backport this everywhere that the |
@nornagon, we only did that in 4-1-x and 5-0-x |
#17694 was abandoned |
Release Notes Persisted
|
I have automatically backported this PR to "4-1-x", please check out #18060 |
I have automatically backported this PR to "5-0-x", please check out #18061 |
I have automatically backported this PR to "6-0-x", please check out #18062 |
Description of Change
Removes the following DLLs from the build, which are only meant to be used for Chromium development:
angle.gni for more details
Follow up to #17694
Checklist
npm test
passesRelease Notes
Notes: Removed Vulkan validation layers DLLs from electron.zip, which are only meant to be used for Chromium development.