-
Notifications
You must be signed in to change notification settings - Fork 136
Package for Android #2
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
Comments
Packaging is partially prepared on dev, outstanding:
|
Would it make sense to have both? E.g. make it possible to use ObjectBox without Flutter (assuming that this a valid use case?) while also having a more convenient Flutter setup.
how so? example? |
It may make sense, but not until the rest of the sentence you quoted could be achieved. At the moment, it wouldn't bring anything.
Not the case after all |
As long our naming does not change... Btw, how do other libs approach this? Do they have two packages? |
From what I've seen it was just a single package. But it seems like it was pretty much just flutter until lately - no "dart-other" stuff so it's no very common yet to support both, except when using plain dart. At pub.dev, you can see what SDK is supported by a package and it's mostly flutter or just plain dart library. I couldn't find any package using FFI and supporting both, not that I tried doing any sophisticated search though :D |
follow up for the only open issue in #73 |
Uh oh!
There was an error while loading. Please reload this page.
Goal: make ObjectBox simple to use when deployed to Android
First, we need to have a binary distribution of the dynamic lib for Android (ObjectBox Java for Android comes with JNI API; not the C API...).
Resources:
Open questions:
Once done: create a ticket to do the same for iOS
The text was updated successfully, but these errors were encountered: