Skip to content

chore: cleanup#11

Open
pwltr wants to merge 4 commits into
masterfrom
chore/cleanup
Open

chore: cleanup#11
pwltr wants to merge 4 commits into
masterfrom
chore/cleanup

Conversation

@pwltr

@pwltr pwltr commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Stop tracking generated iOS XCFramework artifacts in git
  • Move generated iOS release artifacts to dist/ios
  • Keep bindings/ios focused on SwiftPM source/interface files
  • Update Swift package support to iOS 17 only
  • Remove Python bindings and Python build entrypoints
  • Update README and agent docs for the new iOS/Android-only build flow

Details

This cleans up the package layout so generated binary artifacts are no longer committed to the repository. The iOS build now writes:

  • dist/ios/VssRustClientFfi.xcframework
  • dist/ios/VssRustClientFfi.xcframework.zip

while bindings/ios only contains the Swift wrapper source and C interface files consumed by Package.swift.

The Swift package now requires iOS 17+, matching Bitkit iOS’s minimum deployment target and the iOS artifact build configuration.

Python binding support has been removed from the build surface, including build_python.sh, bindings/python, and related README/agent instructions. ./build.sh all now builds iOS and Android only.

Testing

  • Ran ./build_ios.sh successfully and verified the XCFramework is generated under dist/ios
  • Ran shell syntax checks:
    • bash -n build.sh
    • bash -n build_ios.sh
    • bash -n build_android.sh
  • Validated SwiftPM manifest after the iOS 17/tools-version update

@ovitrif ovitrif closed this Jun 15, 2026
@ovitrif ovitrif deleted the chore/cleanup branch June 15, 2026 09:13
@pwltr

pwltr commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

@ovitrif Any reason you closed these PRs?

@ovitrif ovitrif restored the chore/cleanup branch June 16, 2026 10:48
@ovitrif ovitrif reopened this Jun 16, 2026
@ovitrif

ovitrif commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

@ovitrif Any reason you closed these PRs?

By mistake I reckon, sorry for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants