update libskia to chrome/m95 branch, do not require python2 to build from source

fonttools / skia-pathops

Python bindings for the Skia library's Path Ops

https://skia.org/docs/dev/present/pathops/

BSD 3-Clause "New" or "Revised" License

47 stars 14 forks source link

update libskia to chrome/m95 branch, do not require python2 to build from source #49

Closed anthrotype closed 2 years ago

anthrotype commented 2 years ago

Should fix https://github.com/googlefonts/gftools/issues/415

anthrotype commented 2 years ago

Note that we still won't be able to provide pre-compiled wheels for arm64 M1 macs, because Github doesn't provide hosted VMs for macOS with M1 architecture yet. But at least we should be able to publish a source distribution tarball that will no longer require python2.7 to build libskia, which I hope will fix the problems while building skia-pathops from source on M1 macs as repored by @eliheuer in https://github.com/googlefonts/gftools/issues/415. But we will only know after somebody actually tries to build using that sdist on an actual M1 machine.

simoncozens commented 2 years ago

Github doesn't provide hosted VMs for macOS with M1 architecture yet.

~~Surely it does - that's how we were able to build them for ttfautohint?~~ OK, correction, it doesn't provide hosted VMs for M1, but it does provide hosted VMs for macOS11 which enables a Universal build.

anthrotype commented 2 years ago

no, we only cross compile for M1 using the x86_64 VM and macOS 11

anthrotype commented 2 years ago

so you're right, we should be able to build them but not test them

anthrotype commented 2 years ago

thanks for the reminder! I'll see what I can do. It's always tricky when one doesn't have a local machine available to test a build but only relying on a remote CI.