Is there a linker option or such that a framework can expose all the public methods of a kLib that it depends on?
That is to say I have an app A that has a dependency on Framework B which in turn has a dependency on kLib C.
Within app A some of the classes from the kLib are exposed but not all of them. (It only exposes classes I’ve explicitly used in framework B)
Perhaps I should be using dynamic libraries, its been a long time since I’ve built iOS apps 😅
Any insight would be appreciated
04/23/2018, 7:02 PM
it is intended mode of operations to only expose methods of application, not from dependencies, as many dependencies could be huge, such as Apple’s APIs. However, one could consider writing complier plugin to do what you need.
04/23/2018, 11:30 PM
Technically iOS frameworks aren’t allowed to have dependencies. In practice they often have them It is up to the application to bundle any of its framework’s dependencies.
04/24/2018, 9:58 AM
Interesting, thanks for the replies. I find it a bit different coming from my gradle / maven dependency utopia 😉. It’s not a huge inconvenience since my klib is rather small anyway.