And hello again,

one painful change, that should probably be done before the first stable release, is change of header inclusion practise in Sofia-SIP.

Currently all headers are installed to a single directory. The target directory is nowadays versioned (/usr/include/sofia-sip-x.yy/), but it still is one directory.

Now the problem is that applications have statements like:

#include <sdp.h>
#include <sip.h>
#include <msg.h>
#include <stun.h>

These are very, very common names and name clashes will be difficult to avoid in the long run. And as these are in external apps, we cannot easily get everybody to use clever ordering of CPPFLAGS to avoid clashes.

Now, have I missed something? I'd be glad to be proven wrong, if we could avoid this transition... :)

Otherwise, what I propose is that, starting from next release (1.11.7, or even already in 1.11.6), all headers would be installed to a common subdirectory that defines the Sofia-SIP namespace in the system -> prefix/include/sofia-sip-x.yy/sofia-sip/). All applications should use include statements like:

#include <sofia-sip/sdp.h>
#include <sofia-sip/msg.h>

We can support old applications easily by adding the 'sofia-sip/' subdir to our pkgconfig .pc file. But the new apps plus old library combination will break. It is therefore important that the library is changed as soon as possible, so applications have time to catch up.

Any objections (or better ideas)?

--
 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

Reply via email to