Conversation
add back in the mac arm build
.github/workflows/build-release.yml
Outdated
| include: | ||
| - os: macos-12 | ||
| platform: 'darwin-x64' | ||
| - os: macos-12 |
There was a problem hiding this comment.
I think you'll probably need to add this platform back into the list here:
Line 104 in 883eb62
There was a problem hiding this comment.
Oh wait, that's just the linux ones, so never mind...
warren-animoto
left a comment
There was a problem hiding this comment.
Makes sense. We'll have to make a new release in this repo so that mediamoto can pull it down by release/tag name (currently 8.15.2).
We should probably do some mediamoto testing (with HEIC and other files) before we push up the updated install_custom_libvips.sh file in that repo because we'll be grabbing this new sharp version in production as well as locally.
3ad466f to
4f64617
Compare
This feature is unsupported on macOS 10.13. Can be removed when the minimum x64 macOS version increases to 10.15.
Mirrors commit libvips/libvips@ee482ca and libvips/libvips@a9e161f.
* Bump deps: heif, rsvg * Add tomli dependency in Docker containers Required by Cargo projects since Meson 1.5.0. Python >= 3.11 have one built-in, older Python versions require either the external `tomli` module or `toml2json` program.
Allows use of the standard crossbuild tooling
This platform was not published to npm and GitHub releases are no longer used. Running 'npm install' on ARMv7 hardware will use the (32-bit) linux-arm package.
This reverts commit d8ce721.
|
My hope with cherry picking commits (aside from getting us more up-to-date) was that the build errors were: and the heif-related patch was updated in this commit: 3f9da07 which also gives us a new version. waiting to see if that passes... 👀 and inclined to pull in more changes So far only wasm has failed... fingers crossed on arm. Happy to delete wasm builds and leave it here if the rest passes... 😅 On macos 12 ones taking forever... & we're not far from the macos-13 commit... 🤔 but also we won't run this often... 👀 |
Oh 😁 to the latest macos-13 commit we go! |
…ell#252) This should help improve support for multiple versions of sharp that use differing versions of libvips running within the same process by ensuring dlopen accesses the relevant shared library.
- rsvg: avoid use of `cargo generate-lockfile` - webp: ignore "latest" webp-rfc9649 tag
* cargo-c: ensure deterministic build
|
Hmm.. arm failure seems related to the heic fix and & we're already on the latest for de265 (i.e. the fix) 🤔 Unfortunately running locally with 🤔 |
|
I'm assuming that the way to read this error is that when we build libde265, that we're accidentally building it for x86_64. You might be able to fix that by setting Alternatively... dunno if this would massively complicate things, but I saw that ARM mac runners are available https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories Also/related of interest: Lines 60 to 69 in 883eb62 arm64-apple-macos11
|
|
Sorry - meant to post why I thought about |
Worth a try anyways 😅 |
Lots of changes since approved c:
.github/workflows/build-release.yml
Outdated
| - 'linux-armv6' | ||
| - 'linuxmusl-x64' | ||
| - 'linuxmusl-arm64v8' | ||
| - 'linux-ppc64le' | ||
| - 'linux-s390x' |
There was a problem hiding this comment.
I'm assuming we've ended up with a bunch of redundant stuff in here from what you've pulled in from upstream, and I think that's probably fine - this fork always had some unused stuff in it. But I think you can probably delete these lines that were added. @warren-animoto does that match your original forking - just build for linux-x64?
There was a problem hiding this comment.
Yes, see 4fe02d8
Apparently I worked directly in the main branch, so the last few commits there are the tweaks I had to do to get this building again last time.
|
If I'm understanding next steps correctly - it's:
🤔 |
Here's the stackimoto change I did last time - I assume we'll need to pass either |
|
That sounds correct to me, I've never really seen the important difference between tags and releases.. great job pushing this through despite the horrible dev loop! I'd approve, but github thinks I shouldn't be allowed to. |
Thanks! @aliking added this some time ago... (i think i only modified the |

Adds back in the mac arm build. @warren-animoto I'm hoping this will be as simple as this, I just re-instated this value that you removed a couple of commits ago.