I would like to achieve a closed dependency, but would it be possible to refer to the following?
Project (A library deployment project) - > A (currently being created) - > C (Realm ver 0.9x)
Project (A Library Deployment Project) - > C (Realm Latest Version, )
I'm trying to create a library, a library that utilizes DB, and DB is Realm.
However, the version of Realm has been upgraded, so I haven't decided yet.
Realm is a future library, so I think there will be more and more projects to be adopted.
However, I would like to fix the library that I am currently building with the current version if possible.
This library is referencing Realm, so it needs to be verified for version upgrade.
It's troublesome, but the Realm version of the project you introduced is half done
I think it's strange to press the version.
Realm referenced by A library refers only to C (Realm ver 0.9x) and
from the project
Make the deployment project invisible and unaffected, with the latest version of Realm
I would like to be able to put in
By the way, it says library, but we are planning to adopt cocoa touch framework.
Dependencies use cocoapods.
Thank you for your cooperation.
ios swift objective-c xcode cocoapods
Realm is currently accelerating development for version 1.0, so there are still changes.
I understand that it's hard to keep up with the upgrade, but I don't recommend fixing it with the current version at all.
If you can't keep up with the version upgrade at a reasonable interval until at least version 1.0, I think it will be difficult to keep using it.Until then, stable CoreData and SQLite are recommended.
Based on the above information, it is a way to fix the version that only uses a certain library, but I think there is no other way but to rename Realm.framework.The library uses a different name than Realm.framework, imported and used as a separate module, so applications are free to use the latest version of Realm.
© 2024 OneMinuteCode. All rights reserved.