<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Sat, Jul 13, 2013 at 2:17 PM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com" target="_blank">tzafrir.cohen@xorcom.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Jul 12, 2013 at 11:30:53PM -0500, Jeffrey Ollie wrote:<br>
> On Fri, Jul 12, 2013 at 9:55 PM, Matthew Jordan <<a href="mailto:mjordan@digium.com">mjordan@digium.com</a>> wrote:<br>
> ><br>
> > Because pjproject itself embeds a number of third party libraries, getting<br>
> > pjproject properly configured for a distribution/environment can be a bit<br>
> > tricky. We've taken the current findings and issues that people have run<br>
> > into and put together a page on the Asterisk wiki here:<br>
><br>
> Sigh... I know that Asterisk has a long history of embedding<br>
> third-party libraries, but for me to seriously consider packaging<br>
> pjproject/pjsip for Fedora everything in the third-party directory has<br>
> got to go.<br>
><br>
> First off, there's MP3 related code in there. Even though it doesn't<br>
> directly include any MP3 encoding/decoding code it's just not a battle<br>
> worth dealing with. Another oddity is that the code only looks like<br>
> it works on Windows by loading a LAME .dll file. In any case, adding<br>
> MP3 support to a project needs to be dealt with through a generic<br>
> plugin architecture (much how like Asterisk deals with codec support<br>
> now).<br>
<br>
</div>[snip a number of other similar issues]<br>
<br>
Those are all issues that should be taken to pjproject's upstream. What<br>
should be fixed is that the configure script should allow (allow?<br>
default to?) using system copies for all of those libraries.<br>
<br>
Speaking of upstream, any progress with getting the code from the Gitub<br>
branch merged Upstream?<br>
<br>
<br>
And again: thanks for the work done on taming pjproject.<br></blockquote><div><br></div><div style>Two points here:</div><div style><br></div><div style>(1) Whether or not pjproject is packaged by distributions isn't the point of my e-mail - that is, in many ways, a separate concern. The goal here is to make sure that you can actually build shared objects from pjproject on a variety of distributions, and that any "gotchyas" in the process of building said shared objects are discovered prior to Asterisk 12 going out the door.</div>
<div style><br></div><div style>(2) As far as removing external libraries from pjproject is concerned, I agree with Tzafrir: that's a decision Teluu would have to make. If we did that ourselves, we would be effectively forking the project permanently. That is not a good thing - a large reason to go with a third party SIP stack instead of writing our own is obtaining the benefit of having an upstream provider of that functionality. I don't think we would make the decision to fork the project lightly.</div>
<div><br></div><div style>If someone would like to modify the configure script to default to system copies of those libraries, that would be a very welcome patch.</div><div><br></div><div style>Matt</div></div><div><br></div>
-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div><div>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div>
</div>
</div></div>