-
Notifications
You must be signed in to change notification settings - Fork 126
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
Tracking: Metadata extration support for both Java and Swift #154
Comments
The C++ metadata extractor library has been released. We're working on improving the C++ user experience so that it's easy to use when building from source code. |
Excellent! Thank you for the update. |
The improvement will focus on non-bazel experiences, such as using CMake. BTW, what is the expected workflow for your use case, like which platform (c++/ swift / java), prebuilt binary or built from source code? |
I'm new to native apps, so I'm not sure what tool is being used under the hood, but I can describe the setup. I've got a React Native app with custom native integration to TFLite, this all builds with default swift/java compilers as far as I know. My project dependencies have been installed from Pods/Maven/npm, so perhaps there's some step in the bundling that compiles source files in there, but this I'm not aware/certain of. My build.gradle refers to using BUCK for compile dependencies:
Does this answer your question? I'm happy to dig a bit further if you give me some direction |
Thanks for your explanation! Seems like the missing piece of work for you is the swift API distributed from Cocoapods. I'll make a note when we planning work for the next quarter. Thanks for the feedback! |
Happy to help! I was starting to expect something more complicated, so I'm looking forward to the cocoapods distribution. |
I would just like to set up an issue to track when this lib can be used to extract labels from a tflite bundle in both iOS and Android. Current support:
For context:
I'm using Firebase ML to manage custom models for my apps, however managing the labels separately from the model is a pain point. I prefer to solve uniformly in both apps to keep things simple, so I need both java and swift implementations to be ready.
The text was updated successfully, but these errors were encountered: