OK to merge the fw? libraries in framework?

[Tor Lillqvist]

While trying to find easy ways to lower the number of (shared)
libraries, which is more or less on the critical path for the Android
work (the stupid run-time linker on Android has a low (from our
perverse perspective) limit on the number of shared libraries that can
be used at a time in a process), I started looking at the libraries
built in the "framework" module (mnemonically and self-documentingly
named fwe, fwi, fwk, fwl and fwm).

Is there any fundamental problem in just shoving all the objects in
framework into one library (for instance the "fwk" one, or one renamed
to the perhaps more logical name "framework")?

My guess is that the framework code might originally have gone into
just one shared library, anybody know the reason why it was split up
into five separate ones?

(Obviously the corresponding component files will have to be merged,
too, and references to the libraries changed to reference fwk (only)
instead in various places.)

--tml