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

Mac Catalyst support #3

Open
chrisballinger opened this issue Jan 16, 2021 · 6 comments
Open

Mac Catalyst support #3

chrisballinger opened this issue Jan 16, 2021 · 6 comments

Comments

@chrisballinger
Copy link

Looks like this hard fork has already made some awesome progress towards addressing long standing issues in the old Mapbox SDK, like offline vector mbtiles, and XCFramework support.

Now that you already support XCFrameworks, supporting Mac Catalyst should be relatively straightforward. Binary components with custom build scripts will need the following additional architectures:

  • x86_64-apple-ios14.0-macabi
  • arm64-apple-ios14.0-macabi

You'll need to target macOS 11.0 (for Mac Catalyst / iOS 14.0) or higher for OpenGL ES support.

Cheers!

@wipfli
Copy link
Contributor

wipfli commented Jul 1, 2022

Would mac catalyst support still be something you are interested in, @chrisballinger?

@ntadej
Copy link
Collaborator

ntadej commented Jul 1, 2022

I see no reason why we would not support this. It's just one more "iOS" platform to build for afaik.

Although developers may be more interested into proper M1 support in the macOS SDK (I still need to figure out how big the difference there is between native iOS and macOS SDKs).

@chrisballinger
Copy link
Author

Ya I'm interested!

I'm currently trying to figure out how to get offline vector mbtiles to work for the 2022 update to iBurn (based on this reference) but Catalyst and macOS support would be great.

@wipfli
Copy link
Contributor

wipfli commented Jul 1, 2022

Sounds like a fun project...

@ntadej
Copy link
Collaborator

ntadej commented Jul 1, 2022

On paper it should be trivial once done by someone familiar with Apple requirements. We can already build the Qt part of the codebase for M1 mac natively so it's just the matter of configuring the macOS and iOS builds properly.

nvanfleet referenced this issue in lyft/maplibre-gl-native Jul 28, 2022
This PR is updating the version of this image's parent (`bionicbase`) to keep this image (`maplibreglnativeprivate`) up-to-date.
It will be merged if all tests pass via `/merge-skip-owners`; if tests do not pass, it will require manual intervention.

For more details please see the [docs about Automatic Updates](https://docs.lyft.net/eng/provisioningdocs/learning/automatic_updates.html).

[Here is what's changed in `bionicbase`](lyft/containers@336a47d...c6be0ea).

REVIEWS WERE BYPASSED
TimSylvester pushed a commit to WetDogWeather/maplibre-gl-native that referenced this issue Aug 16, 2023
@louwers
Copy link
Collaborator

louwers commented Jun 11, 2024

This will be trivial once Bazel has support for it: bazelbuild/rules_apple#658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants