Chris Brody-GMail wrote: > I would like to suggest another idea, to automatically build both a > "full" libevent library and a set of separated libevent parts, until > the next major release.
+1 I think the -levent-core -lev-http approach makes sense, but (quoting Nick Mathewson's email): > I'm no expert on cross-platform dynamic linkers, but is it feasible > (with libtool or otherwise) to arrange things so that we can split > libevent into separate libraries (libevent-core, libevent-http, etc), > while at the same time ensuring that we don't break old code that > searches for a "libevent" library with all the current libevent APIs? IIRC, Chris Brody's suggestion is the only way to do that, as library dependencies are not transitive in some situations (static libraries, and dynamic libraries some platforms). _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
