Evening (gmt+2) all,
On Thu, 9 Feb 2006, Rob Taylor wrote:
Kai Vehmanen wrote:
- sofia-sip/libsofia-sip-ua-glib/
[ ... or ...]
- sofia-sip/libsofia-sip-ua/nua-glib/
I think its worth framing the question in terms of dependancies. If
built with --with-glib, does that make su dependant on glib? could this
be split out? what would the proposed splitting of sofia into multiple
libs look like, and what would their deps be? can we put all the glib
dependant parts in one shlib?
yes, Pekka can correct me if I'm wrong, but splitting the glib-dependant
parts from 'su' is possible. Basicly we provide a separate implementation
of the Sofia event loop interface (su_root), that uses glib as a backend.
Clients can choose which implementation to use. So it could be arranged so
that libsofia-sip-ua-glib would provide both su-root-glib and nua-glib.
But I'm not sure how many would really benefit from this. With a separate
glib lib, a devoted KDE user could theoretically install only
libsofia-sip-ua binary package to her system, and avoid glib this way. But
in real-life, even KDE requires glib nowadays (or will sooner or later due
to common media subsystem).
So that leaves us exactly who? :)
Those building customized systems probably anyways build with
--without-glib, so they wouldn't benefit from a separate sofia-glib
library.
I'm not proposing any answers today, but it'd be good if we could get
Oops, sorry for the quick response I guess. ;)
--
under work: Sofia-SIP at http://sofia-sip.sf.net
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
