-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Mergable Libraries are unsupported #609
Comments
Thanks for reporting this @abarisain! We've merged the fix, and I can do a release if it'd help. But yeah, CocoaPods should probably upgrade first 🙂 |
Thank you for the fast fix! I don't think there is any rush to cut a release. |
Doesn't Cocoapods need a release of Macho to fix the problem there? |
@woodruffw is it possible to release a version with this fix? |
They do, but they're currently on a pretty old version. I'm happy to do a new release in early June however (currently traveling). |
yes please @woodruffw, and then I can create a PR in Cocoapods to update them and use your newest version. |
Please ease up on the maintainer pressure here, we had literally 0 signal from cocoapods that they intend to update this library or merge your PR anytime soon. Those things take time :) |
@goncg007 Would suggest the PR is opened first using a non-tagged version of this library to check that Cocoapods are willing to do this and it doesn't break anything on their end. Once Cocoapods are 👍🏻 and @woodruffw is ready: it could be tagged. |
This is released in 4.1.0, which we made for macOS 15 support (new format for |
Hello!
Apple has introduced mergable libraries with Xcode 15.
As I understand them, they are dynamic frameworks but come with additional metadata allowing them to be statically merged.
It also comes with a new load command,
LC_ATOM_INFO
(code 0x36) https://github.com/llvm/llvm-project/blob/82c5d350d200ccc5365d40eac187b9ec967af727/llvm/include/llvm/BinaryFormat/MachO.def#L80This library doesn't understand this code and fails parsing the binary.
I'm not sure what you could to with it or what you could expose, I just thought I'd let you know as it breaks parsing altogether.
Have a nice day,
Arnaud
PS: I noticed this issue via CocoaPods, which still uses version 2.5 of this library. So, I don't think there's a need to rush this.
The text was updated successfully, but these errors were encountered: