Skip to content

Keep D3D enabled for Skia m149 Windows Release#11

Closed
danielraffel wants to merge 1 commit into
olilarkin:mainfrom
danielraffel:pr/m149-d3d-release-build
Closed

Keep D3D enabled for Skia m149 Windows Release#11
danielraffel wants to merge 1 commit into
olilarkin:mainfrom
danielraffel:pr/m149-d3d-release-build

Conversation

@danielraffel

@danielraffel danielraffel commented May 23, 2026

Copy link
Copy Markdown
Contributor

This is a narrow alternative to the D3D workaround in #7.

When building chrome/m149, Windows Debug completed but Windows Release failed in Skia's D3D backend source. #7 avoids that by disabling Direct3D for now. This keeps skia_use_direct3d = true and applies a small source patch through the existing patch mechanism.

The failure is in GrD3DBackendSurface.cpp: the equal overrides do not line up with the GPU_TEST_UTILS guards used by the base classes on this branch.

Tested in a fork against chrome/m149; the Windows Release job and full release matrix completed. If disabling D3D until Skia fixes this upstream is preferred, this can just be closed.

@danielraffel danielraffel changed the title Patch the Skia m149 D3D release build Keep D3D enabled for Skia m149 Windows Release May 23, 2026
@danielraffel danielraffel force-pushed the pr/m149-d3d-release-build branch from 2e75b61 to 443fefa Compare May 23, 2026 18:26
@olilarkin

Copy link
Copy Markdown
Owner

Folded into #7, which keeps skia_use_direct3d = true and includes your patches/fix_m149_d3d_backend_surface.patch (authorship preserved). Thanks!

@olilarkin olilarkin mentioned this pull request Jun 14, 2026
@olilarkin olilarkin closed this Jun 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants