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.

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

libass: update to 0.13.0 #912

Merged
merged 1 commit into from
Oct 9, 2015
Merged

libass: update to 0.13.0 #912

merged 1 commit into from
Oct 9, 2015

Conversation

avih
Copy link
Contributor

@avih avih commented Oct 9, 2015

No description provided.

@tonytheodore
Copy link
Member

Thanks!

tonytheodore added a commit that referenced this pull request Oct 9, 2015
@tonytheodore tonytheodore merged commit 98a1131 into mxe:master Oct 9, 2015
@avih
Copy link
Contributor Author

avih commented Oct 9, 2015

np.

FWIW, this version of libass doesn't require fontconfig anymore, except on windows XP. It can still be built with fontconfig, but by default it will only use it if it can't use DirectWrite at runtime (to enumerate the fonts).

With DirectWrite, the enumeration should be much much faster (with fontconfig it can sometimes take minutes the first time the application is executed) .

So when MXE decides to drop XP support, libass can drop fontconfig as a dependency.

@tonytheodore
Copy link
Member

Noted, thanks.

@avih
Copy link
Contributor Author

avih commented Oct 9, 2015

This version also drops ENCA support, so the --disable-enca can/should be removed as well (though it doesn't complain if it's there). I verified this locally.

I also just read the libass changelog and MXE's libass.mk, and as far as I can tell, beyond enca, there shouldn't be more stuff to do here.

Apologies for not having the XP comment and the ENCA thingy as part of the PR.

fiesh pushed a commit to fiesh/mxe that referenced this pull request Feb 5, 2016
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.

None yet

2 participants