ipeddle 0.1.0__tar.gz

ipeddle-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+.pytest_cache/
+.ruff_cache/
+.build/
+.swiftpm/
+*.ipa

ipeddle-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

ipeddle-0.1.0/NOTICE

@@ -0,0 +1,27 @@
+ipeddle
+Copyright 2026 Neguiolidas and the ipeddle contributors
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+Third-party software
+--------------------
+
+ipeddle does not bundle third-party code. At setup time it downloads, onto
+the user's machine:
+
+* The Swift toolchain for Linux from swift.org
+  (Apache License 2.0 with Runtime Library Exception).
+* The ld64-compatible linker built by the xtool project, as a prebuilt release
+  archive pinned by version and SHA-256
+  (https://github.com/xtool-org/darwin-tools-linux-llvm, MIT License;
+  LLVM itself is Apache License 2.0 with LLVM Exceptions).
+  Copyright (c) xtool contributors. ipeddle's approach to cross-compiling
+  for iOS on Linux owes a lot to xtool (https://github.com/xtool-org/xtool).
+
+Apple SDKs
+----------
+
+ipeddle never ships Apple software. The iOS SDK is fetched by the user, on
+the user's machine, from a source the user chooses; its use is governed by
+Apple's license terms. ipeddle is not affiliated with or endorsed by Apple
+Inc. iOS, iPhone, Xcode and Swift are trademarks of Apple Inc.

ipeddle-0.1.0/PKG-INFO

@@ -0,0 +1,272 @@
+Metadata-Version: 2.5
+Name: ipeddle
+Version: 0.1.0
+Summary: Build iOS apps (.ipa) on Linux, no Mac or Xcode required — the Gradle of iOS.
+Project-URL: Homepage, https://github.com/Neguiolidas/ipeddle
+Project-URL: Issues, https://github.com/Neguiolidas/ipeddle/issues
+Author: Neguiolidas
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: build,cross-compile,ios,ipa,linux,swift,swiftpm
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Requires-Dist: tomli>=1.1; python_version < '3.11'
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Provides-Extra: icons
+Requires-Dist: pillow>=9; extra == 'icons'
+Description-Content-Type: text/markdown
+
+# ipeddle
+
+**Build iOS apps on Linux. No Mac, no Xcode.**  ·  [Português](https://github.com/Neguiolidas/ipeddle/blob/main/README.pt-BR.md)
+
+ipeddle is to iOS what Gradle is to Android: one command line tool that takes
+your app's source and gives you an installable package. You write a SwiftPM
+app, run `ipeddle build`, and get an unsigned `.ipa` that you can sign and
+install on your iPhone with Sideloadly or AltStore and a free Apple ID.
+
+```console
+$ pipx install ipeddle
+$ ipeddle setup                 # once: Swift for Linux, an iOS linker, the iOS SDK
+$ ipeddle build examples/hello
+==> building Hello (release, iOS 16.0+, dev.ipeddle.example.hello)
+    [5/7] Compiling Hello HelloApp.swift
+    [6/7] Linking Hello
+==> packaging
+ ok  examples/hello/.build/Hello.ipa  (37.6 KB, unsigned) in 2.3s
+$ ipeddle inspect examples/hello/.build/Hello.ipa
+App:        Hello.app  (dev.ipeddle.example.hello)
+Executable: Hello  [arm64]
+Platform:   iOS  min 16.0  (built with SDK 18.6)
+Links:      29 libraries, 146 imported symbols
+Result:     OK
+```
+
+> Status: **alpha (0.1.0)**. Pure-SwiftPM apps (SwiftUI or UIKit, Swift and
+> C/Objective-C targets, resources, binary xcframeworks) build. Read
+> [Limitations](#limitations) before relying on it.
+
+## Requirements
+
+* Linux x86_64 or aarch64 (Ubuntu 22.04/24.04, Debian 12/13, Fedora, RHEL-likes).
+  On Windows use WSL2. On a Mac, just use Xcode.
+* Python 3.10+ and `git`.
+* About 4 GB of free disk for setup (Swift ~2.5 GB, SDK ~0.6 GB, caches).
+* The system libraries the Swift toolchain needs, see
+  <https://www.swift.org/install/linux/> (on Ubuntu:
+  `sudo apt install binutils git libc6-dev libcurl4-openssl-dev libedit2 libgcc-13-dev libstdc++-13-dev libxml2-dev libncurses-dev libz3-dev pkg-config tzdata unzip zlib1g-dev`).
+
+`ipeddle doctor` checks all of this and tells you what is missing.
+
+## Quick start
+
+```bash
+pipx install ipeddle            # or: pip install --user ipeddle ('ipeddle[icons]' to resize app icons)
+# latest from git: pipx install git+https://github.com/Neguiolidas/ipeddle
+ipeddle doctor                  # what is there, what is missing, how to fix it
+ipeddle setup                   # ~5-10 min the first time, mostly downloads
+git clone https://github.com/Neguiolidas/ipeddle && cd ipeddle
+ipeddle build examples/hello --inspect
+```
+
+The `.ipa` is in `examples/hello/.build/Hello.ipa`. To put it on a phone:
+
+1. Install [Sideloadly](https://sideloadly.io) (Windows/macOS) or
+   [AltStore](https://altstore.io).
+2. Plug in the iPhone, drop the `.ipa` in, sign in with your Apple ID (a free
+   one works; apps then expire after 7 days and you re-install).
+3. On the phone: Settings → General → VPN & Device Management → trust your
+   Apple ID. On iOS 16+ also enable Settings → Privacy & Security → Developer Mode.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `ipeddle init DIR` | Creates a minimal SwiftUI app (`Package.swift`, `ipeddle.toml`, `.gitignore`) to start from. |
+| `ipeddle doctor [--deep]` | Checks Python, OS, disk, the toolchain, the linker, the SDK; `--deep` also compiles and links a test program. |
+| `ipeddle setup` | Downloads Swift for Linux and the linker, fetches the iOS SDK, prepares it. Idempotent: re-running only does what is missing. |
+| `ipeddle build [DIR]` | Builds the SwiftPM app in `DIR` into `DIR/.build/<App>.ipa` (`-o` to choose). `-c debug`, `--product`, `--clean`, `--inspect`. |
+| `ipeddle inspect FILE` | Checks an `.ipa` or `.app`: architectures, minimum iOS, Info.plist, embedded frameworks, and that every imported symbol exists in the library it is bound to. `--json` for scripts. |
+| `ipeddle clean [DIR]` | Deletes temporary files, an app's `.build`, or with `--all` everything ipeddle installed. |
+
+Setup options: `--swift DIR` (use a toolchain you have), `--linker FILE`,
+`--sdk DIR` (an `iPhoneOS*.sdk` you have), `--xip FILE` (extract the SDK from
+an `Xcode_*.xip` you downloaded from Apple; only the SDK is written to disk),
+`--sdk-version` (default 18.6), `--force`, `--no-download`. `ipeddle clean
+--cache` empties the shared module cache. Everything lives
+in `$IPEDDLE_HOME` (default `~/.local/share/ipeddle`).
+
+## Making an app ipeddle can build
+
+An ipeddle app is a regular Swift package with an executable product and an
+iOS platform. See [`examples/hello`](https://github.com/Neguiolidas/ipeddle/tree/main/examples/hello):
+
+```swift
+// swift-tools-version: 5.9
+import PackageDescription
+
+let package = Package(
+    name: "Hello",
+    platforms: [.iOS(.v16)],
+    products: [.executable(name: "Hello", targets: ["Hello"])],
+    targets: [
+        .executableTarget(name: "Hello", resources: [.process("Resources")]),
+    ]
+)
+```
+
+The `@main` SwiftUI `App` (or a UIKit `UIApplicationMain`) lives in the
+executable target. App settings go in an optional `ipeddle.toml`:
+
+```toml
+[app]
+product = "Hello"                     # which executable product to package
+bundle-id = "com.example.hello"       # default: dev.ipeddle.<product>
+display-name = "Hello"
+version = "1.0.0"                     # CFBundleShortVersionString
+build = "1"                           # CFBundleVersion
+icon = "Icon.png"                     # square PNG, 1024x1024 recommended
+info-plist = "Info.plist"             # extra keys (permissions, URL types...); $(VARS) are expanded
+resources = ["Extra"]                 # files/folders copied into the .app as-is
+device-family = ["iphone", "ipad"]
+swiftc-flags = []
+```
+
+## How it works
+
+Apple's toolchain is open source; what makes "iOS on Linux" hard is
+everything around it. ipeddle puts these pieces together on your machine:
+
+1. **Compiler.** The official Swift toolchain for Linux already contains
+   `swiftc`, `clang` and `llvm-ar` with the ARM64/Darwin backends.
+2. **Linker.** The Linux toolchain's `ld64.lld` refuses iOS, so setup downloads
+   the ld64-compatible `lld` that the [xtool](https://github.com/xtool-org/xtool)
+   project publishes.
+3. **SDK.** Headers, `.swiftinterface` files and `.tbd` stubs for iOS. By
+   default setup makes a sparse, shallow `git` checkout of a public mirror
+   (only the one SDK folder, a few hundred MB). You can point it at an SDK you
+   already have, or at an `Xcode.xip` (streamed: only the SDK is extracted).
+4. **SDK patches, generated on your machine.** Public SDK mirrors carry
+   *reconstructed* `.tbd` stubs that describe the newest iOS layout, so a
+   naively linked app crashes on older iOS. ipeddle copies the SDK (hard links,
+   so it costs almost no disk) and rewrites the stubs with rules derived from
+   the SDK itself, never from a hand-made list:
+   * **Swift overlays.** Until iOS 17 the Swift half of a framework
+     (`Foundation`'s `Data`, `URLRequest`...) lived in
+     `/usr/lib/swift/libswiftFoundation.dylib`; since iOS 18 it lives in the
+     framework. Every Swift symbol whose mangled name says it belongs to module
+     *X* is moved from the framework's stub to `libswiftX`'s stub. Binding
+     through the overlay works on both old and new systems.
+   * **Split frameworks.** Declarations moved to a new framework keep their
+     original mangling (`@_originallyDefinedIn`), e.g. `SwiftUICore` split
+     out of `SwiftUI` in iOS 18. Such symbols are moved back into the parent
+     that re-exports the child, so the app never links the child and still
+     launches on iOS 15-17.
+   * **Missing symbols.** If the link fails on Swift symbols the stubs do not
+     list at all, ipeddle works out the owning module from the mangled name,
+     declares them in that module's overlay, and relinks. What it learns is
+     kept in the patched SDK for every later build.
+5. **Runtime bits.** Xcode ships `libclang_rt.ios.a`; ipeddle compiles the
+   one routine apps need from it (`__isPlatformVersionAtLeast`, used by
+   `#available` / `@available`) from its own source at setup.
+6. **Build and package.** `swift build` cross-compiles with a generated Swift
+   SDK bundle; ipeddle then assembles `Payload/<App>.app` (binary, resource
+   bundles, frameworks, Info.plist, icons) and zips a reproducible `.ipa`.
+
+### Caching
+
+* The SDK's Swift and Clang modules (Swift, Foundation, UIKit, SwiftUI...) are
+  compiled into **one module cache shared by all your apps**. Setup ends with a
+  test compile that also fills it, so even the first build of a new app is fast.
+* SwiftPM's incremental build does the rest; the `.ipa` step takes milliseconds.
+* When the SDK stubs change (re-setup, learned symbols), the next build relinks.
+
+Measured on a 16-core Linux box with `examples/hello`:
+
+| Build | Time |
+|---|---|
+| very first compile, empty module cache | 68 s |
+| first build of an app after `ipeddle setup` (cache filled by setup) | 2.0 s |
+| `--clean` rebuild | 2.1 s |
+| rebuild with no changes | 0.7 s |
+
+## Limitations
+
+Honest list. Some are fundamental, some are just not done yet.
+
+* **No code signing.** The `.ipa` is unsigned. Sideloadly/AltStore sign it
+  with your Apple ID; App Store / TestFlight distribution still needs Apple's
+  tools and a paid developer account.
+* **No asset catalogs (`actool`).** `.xcassets` cannot be compiled. ipeddle
+  falls back: the app icon is taken from `icon` (or the largest PNG of an
+  `AppIcon` set), and image sets are bundled as loose `name@2x.png` files,
+  which `UIImage(named:)` and `Image("name")` find. Color sets, data sets and
+  symbol sets are not supported; define them in code.
+* **No Interface Builder (`ibtool`).** Storyboards and XIBs are not compiled;
+  build UI in code (SwiftUI or UIKit). The launch screen comes from
+  `UILaunchScreen` in Info.plist.
+* **SwiftPM projects only.** `.xcodeproj` / `.xcworkspace` projects are not
+  read. CocoaPods are not supported; SwiftPM dependencies and binary
+  `.xcframework` targets are.
+* **Device builds only** (arm64). There is no iOS Simulator on Linux.
+* **iOS 15 or newer.** Older deployment targets need back-deployment
+  libraries that only ship with Xcode.
+* **Public SDK caveats.** The symbol rules are derived from the SDK and
+  `examples/hello` (SwiftUI, Foundation, a C target with `#available`) and a
+  UIKit + PhotosUI app built from the 18.6 SDK were launched on iOS 16.7, but
+  the rules are heuristics over reconstructed stubs: a symbol that lived in a different library on some
+  older iOS version than the stubs suggest will fail at launch on that
+  version. `ipeddle inspect` catches symbols the SDK does not export at all,
+  not this case. Test on the oldest iOS you support.
+* **Macros.** Macros that ship with the Swift toolchain (`@Observable`,
+  `#Predicate`...) work; SwiftUI's `#Preview` and other Apple-only macro
+  plugins do not (remove `#Preview` blocks or wrap them in `#if DEBUG` checks you
+  do not build).
+* **Embedded dynamic frameworks** (from binary `.xcframework` targets) are
+  packaged the way Xcode does it (`Frameworks/`, stripped of headers and
+  modules, `@executable_path/Frameworks` rpath) and pass `ipeddle inspect`,
+  but have not yet been launched on a real device.
+* **Less-tested inputs.** Development used the public mirror's 18.6 SDK.
+  SDKs extracted from an Xcode `.xip` use the same code path but have had
+  less testing; downloads are checked for completeness, not signatures.
+* **No dSYMs** (`-debug-info-format none`), so crash logs are not symbolicated.
+* SwiftPM prints a deprecation warning for the `native` build system that
+  ipeddle uses; a future Swift release may require changes.
+
+## Legal
+
+ipeddle is licensed under the Apache License 2.0 and contains no Apple
+software. The iOS SDK is downloaded by **you**, onto **your** machine, from a
+source **you** choose, and Apple's license terms apply to it (Apple's Xcode
+and SDK agreement allows use on Apple-branded computers; whether and how you
+may use the SDK elsewhere is between you and Apple). ipeddle does not
+redistribute SDK files and the patched copy never leaves your machine.
+
+ipeddle is not affiliated with, endorsed by, or sponsored by Apple Inc.
+iOS, iPhone, iPad, Xcode and Swift are trademarks of Apple Inc.
+
+## Acknowledgements
+
+* [xtool](https://github.com/xtool-org/xtool) (MIT) pioneered Xcode-free iOS
+  builds on Linux; ipeddle downloads its ld64-compatible linker.
+* The [Swift project](https://swift.org) for the Linux toolchain.
+
+## Contributing
+
+```bash
+pip install -e '.[dev]'
+ruff check src tests
+pytest
+```
+
+Unit tests use synthetic `.tbd`, Mach-O and `.xip` fixtures generated in the
+tests themselves; no Apple files are needed or allowed in the repository.