Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Baseline regression: CI file conflicts from mesa's new libegl on windows #39198

Closed
dg0yt opened this issue Jun 10, 2024 · 1 comment
Closed

Baseline regression: CI file conflicts from mesa's new libegl on windows #39198

dg0yt opened this issue Jun 10, 2024 · 1 comment
Assignees
@JonLiu1993
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@dg0yt
Copy link
Contributor

dg0yt commented Jun 10, 2024 •
edited
Loading

Since #37599, mesa causes conflicts:

error: The following files are already installed in D:/installed/x64-windows and are in conflict with mesa:x64-windows

Installed by angle:x64-windows
bin/libEGL.dll
    debug/bin/libEGL.dll
    debug/bin/libEGL.pdb
    debug/lib/libEGL.lib
    lib/libEGL.lib

Installed by egl:x64-windows
debug/lib/pkgconfig/egl.pc
    lib/pkgconfig/egl.pc

https://dev.azure.com/vcpkg/public/_build/results?buildId=103751
https://dev.azure.com/vcpkg/public/_build/results?buildId=103753
@dg0yt dg0yt mentioned this issue Jun 10, 2024
Merged
BillyONeal pushed a commit that referenced this issue Jun 10, 2024
@dg0yt
[vcpkg baseline][mesa] Remove egl from default features (#39199)
c37a878 
Mitigation for #39198.

Mesa CI is currently disabled for linux and osx, and also doesn't run
for android.
So we see CI effects only for Windows. Improving CI situation for mesa
is the subject of #36081. So keeping egl out of CI like before
#37599 is the best option at the
moment.
@JonLiu1993 JonLiu1993 added the category:port-bug The issue is with a library, which is something the port should already support label Jun 11, 2024
@JonLiu1993
Copy link
Member

Fixed by PR #39199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonLiu1993 JonLiu1993

Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dg0yt @JonLiu1993