-
Notifications
You must be signed in to change notification settings - Fork 1
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
Automate installation of libimobiledevice #71
Comments
The GitHub releases (https://github.com/libimobiledevice/libimobiledevice/releases/tag/1.3.0, https://github.com/libimobiledevice/ideviceinstaller/releases/tag/1.1.1) unfortunately only have the source code, no binaries. |
Brew also builds from source: |
Amusingly enough, this would actually be easiest on Windows. :D In tweaselORG/meta#25, I found https://github.com/L1ghtmann/libimobiledevice/releases, which you only need to download and extract. |
The libimobiledevice CI actually even produces archives, but only uploads those as artifacts and not as releases. And those are deleted after 90 days. :/ But even if we did have those, we would still need the other dependencies like libplist3. And they all don't just have binaries but also shared libraries (and maybe other important stuff that I missed?). |
Oh, and before I forget: We also need libusbmuxd6. :| |
This really looks like it will take more time than I can spend on it right now. |
One more thought: Doesn't palera1n bundle limd? |
Looks like they built their own static binaries and bundled them in the repo. At least for the legacy version, I haven't looked into the rewrite yet (though I guess they would target the limd libraries instead of CLI for that?). https://github.com/JonathonReinhart/staticx looks interesting. |
Not necessary anymore with #84. |
With andromatic and #69, we're now automatically installing the Android dev tools. Wouldn't it be fun to have that for iOS, too?
In terms of host dependencies on iOS, there's pretty much only libimobiledevice and the device drivers on Windows. Let's see whether we can do something similar for the former.
The text was updated successfully, but these errors were encountered: