What about listing the libDir and fetching all .so files? It'd solve this issue even for other recipes. Also, is there a possibility that the NDK would generate versioned libs? If yes, then the approach will probably fail: libmy.so.1.

@KeyWeeUsr There have been complaints about auto loading all libs here #903 (comment)

Nevertheless. It would be great if there was a way to explicitly define libs to be loaded in the specs file or so.

@KeyWeeUsr I thought about that, and I don't actually agree with @akshayaurora's objection (it seems to me that anyone who can place .so files for automatic loading can probably also just modify an existing one), but went for the extra explicit option instead. Automatic loading would also have the problem that we'd still need to impose some ordering on what is loaded when, so it wouldn't be possible to be completely naive about it.

I'm thinking to add a Recipe attribute that specifies .so files which will be produced, then to try to load them according to the recipe build order. I guess this will normally be correct. But, if this works, I think it's mergeable as it is to fix the issue for now.