After building a specially-linked version of code module(s), a tool inspects the resulting symbol table for unsatisfied dependencies, and aggregates them into a linker script, to ensure that those (and only those) methods are given global visibility.
The current static linker script(s) need to be made dynamically, possibly using templates to represent the JNI methods currently listed in the scripts.
The speed of the prototype python script should be assessed to see whether a C++ version of the tool is worthwhile.
Comment 1 by bugdroid1@chromium.org
, Nov 21