You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be an issue with macOS SDK compatibility when trying to install enable 5.3.1 in a fresh virtualenv if using the macports supplied python 3.10.9. I'm successful using Apples python 3.9 that ships as part of the Xcode commandline tools, though.
A similar issue seems to apply to other open source projects (I found https://trac.macports.org/ticket/66095), where a proposed solution was to set the macos deployment target to 12.0. Not sure if that is desired here – instead, it might be necessary to make kiva build against current, non-deprecated APIs.
We're hoping to get rid of the SWIG-based Agg and FreeType since they are very, very old, and replace them with Celiagg, so we're probably not going to spend a lot of time upgrading the APIs as the time would be better spent adapting to the newer wrapper.
Independently there looks like there may be other issues with building kiva via pip right now.
A little digging since I am seeing some (different) build errors - it looks like on OSX it's looking for headers in a Framework-based header directory, which may be a factor in why the build against Apple's python works but macports doesn't.
There seems to be an issue with macOS SDK compatibility when trying to install enable 5.3.1 in a fresh virtualenv if using the macports supplied python 3.10.9. I'm successful using Apples python 3.9 that ships as part of the Xcode commandline tools, though.
A similar issue seems to apply to other open source projects (I found https://trac.macports.org/ticket/66095), where a proposed solution was to set the macos deployment target to 12.0. Not sure if that is desired here – instead, it might be necessary to make kiva build against current, non-deprecated APIs.
Here is how it looks using Apple's python 3.9:
Here is how it looks using macports' python 3.10:
The text was updated successfully, but these errors were encountered: