On Wed, May 6, 2009 at 6:26 PM, David Daney <dda...@caviumnetworks.com> wrote: > Ralf Wildenhues wrote: >> >> Hello Dave, >> >> * Dave Korn wrote on Wed, May 06, 2009 at 06:09:05PM CEST: > > [...] >>> >>> 1) Would this be a reasonable approach, specifically i) in adding a >>> configure >>> option to cause sublibraries to be built, and ii) in using gmake's >>> $(filter) >>> construct to crudely subdivide the libraries like this? >> >> You are aware of the fact that it is part of the ABI in which of the >> linked DLLs a given symbol was found, and any shuffling of that later >> will break that ABI? >> >> You also have to ensure that the sub libraries are self-contained, or at >> least their interdependencies form a directed non-cyclic graph (or you >> will need very ugly hacks on w32). >> > > Unfortunately it may not be a simple task to find a suitably large set of > packages that satisfy this 'directed non-cyclic graph' criterion. > > I might suggest looking at grouping a bunch of various protocol handlers > together that are all accessed via mechanisms like the URLConnection, and > the various crypto implementations.
Is it not that maybe most of the exported symbols are not necessary and can be made hidden? Richard.
