Re: Softphones and arm builds with latest ccrtp, and exosip2 arm builds are broken

David Sugar <[email protected]>
Newsgroups gmane.comp.gnu.ccrtp.devel
Message-ID <[email protected]>
I am always glad when we do not break other packages :).  Hmm...Twinkle
has it's own sip stack?

Michel de Boer wrote:
> Hi David,
> 
> Thanks for this confirmation. It was still on my todo list to
> build Twinkle against the latest libarries.
> 
> Cheers,
> Michel
> 
> David Sugar wrote:
>> I have now also successfully built Twinkle without issues against
>> current CommonC++/ccrtp...
>>
>> David Sugar wrote:
>>> I have been able to successfully build sflphoned/sflphone-qt against the
>>> latest commoncpp2 (1.4.1) and ccrtp (1.4.0), and I will try to do the
>>> same with twinkle next.  I also have been able to successfully build
>>> ccrtp without difficulty on arm for ipaq for gpe/opie/qtopia.
>>>
>>> While I had no problem with libosip2, I have not been able to
>>> successfully cross-compile libeXosip2 for arm as yet, and I get many
>>> very odd bugs and errors in places that do not even make immediate sense
>>> to me.  This means probably neither sflphone nor twinkle will port
>>> successfully at this time, since they both also make use of exosip2 code.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Ccrtp-devel mailing list
>>> [email protected]
>>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
>>> _______________________________________________
>>> Ccrtp-devel mailing list
>>> [email protected]
>>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
>

_______________________________________________
Ccrtp-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/ccrtp-devel
dyfet.vcf (text/x-vcard, 177 B)
begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:[email protected]
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.