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
Thanks for the suggestion - but I'm not even sure what this would mean. Python-Apple-support is a library that you would include in your iOS project... unless I'm missing something, it shouldn't matter whether your project is a Catalyst project or a Cocoa project - you link in the Python support library, and invoke it as required.
What exactly is it that you think needs to be added?
Yes but to be able to link the python library when building an app for catalyst the library itself needs to be built specifically for catalyst as well. iOS or macOS libraries can't be used in catalyst builds.
To build a library for catalyst you have to build against the macOS SDK and specify a target in the form x86_64-apple-ios13.0-macabi, with the arch and iOS version adjusted as needed.
Ah - I didn't realise Catalyst was based on an entirely different ABI.
Catalyst isn't a huge priority for me personally, but if you wanted to add another target platform to support Catalyst, I wouldn't object to a PR that added it.
@freakboy3742 Is it okay if I reimpl. the Catalyst Support stuff on this PR? A bunch of changes are needed for the logic and I think it'll be easier for me to start a separate PR to here.
Activity
freakboy3742 commentedon Apr 11, 2021
Thanks for the suggestion - but I'm not even sure what this would mean. Python-Apple-support is a library that you would include in your iOS project... unless I'm missing something, it shouldn't matter whether your project is a Catalyst project or a Cocoa project - you link in the Python support library, and invoke it as required.
What exactly is it that you think needs to be added?
JonasGessner commentedon Apr 12, 2021
Yes but to be able to link the python library when building an app for catalyst the library itself needs to be built specifically for catalyst as well. iOS or macOS libraries can't be used in catalyst builds.
To build a library for catalyst you have to build against the macOS SDK and specify a target in the form
x86_64-apple-ios13.0-macabi, with the arch and iOS version adjusted as needed.freakboy3742 commentedon Apr 13, 2021
Ah - I didn't realise Catalyst was based on an entirely different ABI.
Catalyst isn't a huge priority for me personally, but if you wanted to add another target platform to support Catalyst, I wouldn't object to a PR that added it.
freakboy3742 commentedon Mar 16, 2025
For anyone interested in adding MacCatalyst support, user @asavva-2016 was working on a series of patches to implement this feature:
These were getting close to being ready to merge, but @asavva-2016 wasn't able to commit the time to get them over the line.
freakboy3742 commentedon Apr 23, 2025
The first part of this work - adding macCatalyst binaries to cpython-apple-source-deps - has now been done.
johnzhou721 commentedon Apr 27, 2025
@freakboy3742 Is it okay if I reimpl. the Catalyst Support stuff on this PR? A bunch of changes are needed for the logic and I think it'll be easier for me to start a separate PR to here.
freakboy3742 commentedon Apr 27, 2025
@johnzhou721 I'm confused about what you're asking. This isn't a PR, and there isn't an open PR for Catalyst support...
johnzhou721 commentedon Apr 27, 2025
Oh I was wondering if (when) I do the building stuff for mac catalyst if I could not base my code on #256 and start a separate PR.
freakboy3742 commentedon Apr 28, 2025
Use #256 if it's helpful; if it's not, don't. I don't mind either way.