Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Keroulas <patrick.keroulas@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] pjsip package status
Date: Mon, 22 Feb 2016 17:21:54 -0500 (EST)	[thread overview]
Message-ID: <841623823.459573.1456179714125.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20160220173543.GE3418@free.fr>

Yann, 

Sure I can take a look at this but my BR experience is quite limited. 
Not sure about gsm, srtp, and portaudio. Why aren't they treated like other options? Are you sure they're necessary for Asterisk application? 
I thought configure options should limit the package footprint as much as possible. 

Regards, 

-- 
Patrick Keroulas 
Consultant en logiciel libre, 
Savoir-faire Linux Inc. 

7275 Saint-Urbain, bureau 200 
Montr?al, Qu?bec H2R 2Y5 
t?l: (514) 276-5468 ext. 167 
fax: (514) 276-5465 
_____________________ 


From: "Yann E. MORIN" <yann.morin.1998@free.fr> 
To: "Patrick Keroulas" <patrick.keroulas@savoirfairelinux.com> 
Cc: "buildroot" <buildroot@busybox.net> 
Sent: Saturday, February 20, 2016 12:35:43 PM 
Subject: Re: [Buildroot] pjsip package status 

Patrick, All, 

On 2016-02-17 15:04 -0500, Patrick Keroulas spake thusly: 
> Regarding pjsip package ( [1]http://lists.busybox.net/pipermail/buildroot/2015-April/126960.html ), is there any reason why it's not 
> part of the package collection yet? 

You may want to have a look at my in-proress series that adds Asterisk. 
The last few patches are to add pjsip. 
https://git.buildroot.org/~ymorin/git/buildroot/log?h=yem/asterisk 

Please have a look and provide your feedback. 

I will probably send that series shortly afte rthe next release is cut 
(i.e. in errly March). 

Regards, 
Yann E. MORIN. 

> Regards, 
> -- 
> Patrick Keroulas 
> Consultant en logiciel libre, 
> Savoir-faire Linux Inc. 
> 
> 7275 Saint-Urbain, bureau 200 
> Montr?al, Qu?bec H2R 2Y5 
> t?l: (514) 276-5468 ext. 167 
> fax: (514) 276-5465 
> _____________________ 
> 
> Links: 
> 1. http://lists.busybox.net/pipermail/buildroot/2015-April/126960.html 

> _______________________________________________ 
> buildroot mailing list 
> buildroot at busybox.net 
> http://lists.busybox.net/mailman/listinfo/buildroot 


-- 
.-----------------.--------------------.------------------.--------------------. 
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | 
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | 
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | 
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | 
'------------------------------^-------^------------------^--------------------' 
_______________________________________________ 
buildroot mailing list 
buildroot at busybox.net 
http://lists.busybox.net/mailman/listinfo/buildroot 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160222/45bde57e/attachment.html>

  reply	other threads:[~2016-02-22 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 20:04 [Buildroot] pjsip package status Patrick Keroulas
2016-02-17 21:05 ` Thomas Petazzoni
2016-02-20 17:35 ` Yann E. MORIN
2016-02-22 22:21   ` Patrick Keroulas [this message]
2016-02-22 22:33     ` Yann E. MORIN
2016-02-23 16:53     ` Luca Ceresoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=841623823.459573.1456179714125.JavaMail.zimbra@savoirfairelinux.com \
    --to=patrick.keroulas@savoirfairelinux.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox