It is no longer safe to assume that there's only a single library built with a specific name now that we have a split between the system and vendor partition. I highly recommend using the Android build system to do your compilations so that you don't need to stay on top of changes like this -- these libraries moving is just one of the many things that changed in how to build a library to install into /vendor over the last several years. At some point they'll no longer exist in the obj/SHARED_LIBRARIES path you found below as we move away from Make and to Soong, which uses even less stable intermediate paths.
- Dan On Wednesday, January 16, 2019 at 5:08:45 PM UTC-8, Dimitrije Petrovic wrote: > > After migration to Android P many vendor libraries have missing > dependencies because libraries they are missing from *$OUT/obj/lib/*. > These files can be found in > *$OUT/obj/SHARED_LIBRARIES/<libname>_intermediates/* folders and can be > copied. But this isn't a convenient way of resolving dependencies and it's > basically impossible to keep them up to date. > > Anyone have an idea why this is happening? > On Android O these problems were not present and all .so and .so.toc files > were present in *$OUT/obj/lib/.* > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
