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
Use official metal sources #7341
Labels
Comments
While I agree moving to official Angle would be good I think it's not as simple as that. MGLKit API is not part of official Angle so the adapter framework would need to be created. kakashidinho/metalangle#81 discusses this possibility but it seems the author doesn't have the time to work on it which suggests it's not such a low effort task. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The metal sources currently used by the robovm-metalangle backend are coming from a dead repo, see readme.
Libgdx should - at some point - use the official sources as they now cover a wider compatibility as the fork currently used.
The only issue is that there are no release binaries as far as I can see, so those would need to be built first, but the workflow files for this are in the fork repo, so shouldn't be too much effort.
The text was updated successfully, but these errors were encountered: