-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
ci: Add Windows Clang builder #412
Conversation
these takes a lot of time and will timeout on ci
Currently we have to commit directly to the |
Does this workaround still work? actions/checkout#135 (comment)
|
No. I've tried it with multiple variants and it insists to checkout as crlf, and the maintainer of the checkout CI action has strong preference on directly committing it into the |
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.
LGTM as long as it works 😄
The libass/vf_subtitles seems unhappy: (font provider fontconfig)
mingw build: (font provider directwrite (with GDI))
|
I enabled directwrite and libass is working now. |
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.
YOLO
This adds a Windows native msys2 builder to CI which uses the clang64 environment and build the whole dependency chain with clang instead of gcc.
The dependencies are utilizing the makepkg build system and using the patches directly come from msys2. This way we can workaround known quirks for clang on windows easier and only care about to actually modify the build configs and pin to specific version we want.
Currently, most of the packages are pulled with versioned tarball instead of direct git commit pin.
This version includes all dependencies that the one built by our current docker builder has.
Current quirk of this version is that the
--enable-shared
option cannot be enabled for this as clang 's lld is not happy with the libfreetype being linked multiple times in a shared library, and we have to use static build all the way.Changes
Issues