|
Well.... The whole problem with FAT is the SO names no longer ACTUALLY point to their long SO counterparts, they are in fact a copy of the long-named so versions since FAT does not support links. Neatly and effectively breaking the SO name fail-over system.
This makes the task of providing ALL libs in one place impractical.
however many libs get used again and again - and the modules required for the 3 different flavours of kernel we have don't change so those things will make it into KUAL-system.
so - in a nutshell - those libs required to provide the support for the systems binaries provided by kual-system will indeed go into /mnt/us/extensions/system/lib/armv7l /mnt/us/extensions/system/lib/armv6l and /mnt/us/extensions/system/lib
and the relevant LD_LIBRARY_PATHs are added to the main.
if people choose to then put bits of their libs in there then they would indeed be instantly resolved, but this is not a long term, or stand-alone, solution for the problem of library duplication and a /mnt/us/extensions/my_app/lib/ folder would be required in most cases to ensure libs are available - other than those libs that end up being staple libs for the kual-system itself.
Hope that is clear if not that helpful.
|