tensorflow / tensorflow/tflite-support

Generate XCFframework and Static library usage over Swift

Open
#921 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
441
Forks
146
PR merge metrics
No merged PRs in 30d

Description

Hello world!

Im in need of some assistance and would like to know if anyone could help. Is it possible to distribute the TensorFlowLiteTaskVision using XCFframework ? Would it be just a matter of compiling the framework for the different architectures (like sim arm64 x86 and arm64) and packaging with xcodebuild create framework flag ?

Also, Im lost on how to use the static generated library (iOS_static_framework) over swift. The only asset generated is the .a file and after I imported it on to the project, swift doesn't recognized that module since there is not module definition like the dynamic framework has.

Is there any example on usage on how to import/use the TensorFlowLiteTaskVision.a ?

Thanks a bunch in advance!

Kind regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the TensorFlowLiteTaskVision distribution question and the generated iOS_static_framework .a artifact; compare the requested XCFramework packaging and Swift import path. Done means documenting whether XCFramework distribution is supported and providing a verified Swift usage example for the static library.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
build-system, mobile-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.