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
Catalyst support #2799
Comments
|
example:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
#2801 is in progress but can already build xcframeworks with I'm not sure what we're supposed to do with dSYMs |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This should mean that we can stop using |
@mdiep as far as I can tell yes. But I'm not sure how dsyms will be packaged. |
Hey guys, I was just wondering was there a resolution to this problem? |
It looks like dSYM files are inside each architecture package. |
Hello, any ETA planned for this feature? |
CocoaPods recently added support for xcframeworks in 1.9.0, we (PSPDFKit) sponsored part of the development. Would anyone be interested in a similar agreement? |
I’d be happy to implement Catalyst functionality on my employer’s time but I am worried that Carthage has no forward movement. There are multiple other pull requests that seem to be stuck. |
@DavidBrunow which ones? I have merged quite a few recently. Please contact me on twitter about this https://twitter.com/tmpz I also have contacted @steipete since I have some time on my hands but I can't guarantee it will be enough. |
@tmspzz Sorry I was wrong about the pull requests not being merged -- I hadn't noticed that they had been. But we are still waiting on a release for those pull requests so I'm still worried. |
I just tried to install a binary xcframework via Carthage. It installed the simulator .framework slice and threw out the arm .framework slice. |
* [CHANGED] The SumUp SDK is now a dynamic framework and is shipped as an XCFramework. If you had previous versions installed, check out the Migration Guide. * [CHANGED] The `SMPSharedResources.bundle` is now part of the XCFramework and should not be added to the app target * Warning: The latest Carthage (0.35.0) is not yet compatible with XCFrameworks (see Carthage/Carthage#2799) Sample application: * [UPDATE] Remove `-ObjC` from Other Linker Flags
is carthage dead? or will a fix come one day? |
Probably is :D I had to switch to spm because I can't wait anymore |
It's most certainly not dead. XCFramework support is actually now on |
Ah wonderful! Any ETA for a public release? |
looks like the changes are released in today's 0.37 release. |
|
Now that we have |
Happy to sponsor Catalyst slice support, please feel to contact me via Twitter @hansemannnn! |
I pushed a working implementation: #3235 Not quite ready to be merged yet, but if you want to try it out in your project, feel free to clone it and |
Apparently in order for this to work Carthage will need to build
.xcframework
s now: https://twitter.com/NeoNacho/status/1135691439734575104.The text was updated successfully, but these errors were encountered: