Re: [Freeswitch-dev] [Freeswitch-users] FreeSWITCH Unstable Repo
For core freeswitch, likely yes. For the deps, someone will have to do the work and find out. I'd prefer to do this under cowbuilder along side how we build for all other platfroms, but someone will need to do the work to figure out what all exactly is necessary to make it happen.
On Jun 18, 2015, at 11:23 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Does cross-compiling work? Because building arm packages on an arm server takes about 6 hours.
On Jun 18, 2015 4:45 PM, "Brian West" <brian@freeswitch.org <mailto:brian@freeswitch.org>> wrote: If the community steps up and assists on this front we can expand our target platforms to non-x86, ubuntu, and various others... We'll have the RPM based unstable repo soon too. Ken is wrapping that up soon.
So anyone wanting to get involved please email us.
On Thu, Jun 18, 2015 at 9:34 AM, jungle Boogie <jungleboogie0@gmail.com <mailto:jungleboogie0@gmail.com>> wrote: On 18 June 2015 at 07:18, Brian West <brian@freeswitch.org <mailto:brian@freeswitch.org>> wrote:
To help speed the testing and release cycle up, Team FreeSWITCH has created a FreeSWITCH Unstable Debian repo, This repo is updated after every commit to master and the debs lag behind about an hour from each commit.
Wow, this is really wonderful.
Are you considering also packages for non x86 platforms, too? Specifically arm.
-- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info <mailto:jungleboogie@sip2sip.info> xmpp: jungle-boogie@jit.si <mailto:jungle-boogie@jit.si>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/>
-- Brian West brian@freeswitch.org <mailto:brian@freeswitch.org>
Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com <http://www.freeswitchbook.com/> http://www.freeswitchcookbook.com <http://www.freeswitchcookbook.com/> ClueCon 2015 Call for Speakers <https://www.cluecon.com/call-for-speakers/> | Register <https://freeswitch.com/cart.php?gid=1> TODAY! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> T:+19184209001 <tel:%2B19184209001> | F:+19184209002 <tel:%2B19184209002> | M:+1918424WEST (9378) iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/> _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Michael Jerris <mike@jerris.com> wrote in news:39F9F70C-6B5C-4F5D-9B49-7F08BDCB08E4@jerris.com:
--Apple-Mail=_703FC8B5-A831-4CD2-BE6F-9D24BE0DE535 For core freeswitch, likely yes. For the deps, someone will have to do the work and find out. I'd prefer to do this under cowbuilder along side how we build for all other platfroms, but someone will need to do the work to figure out what all exactly is necessary to make it happen.
On Jun 18, 2015, at 11:23 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Does cross-compiling work? Because building arm packages on an arm server takes about 6 hours.
Hi, please excuse me if my posting is better suited for the -users mailinglist. When it comes to cross compiling maybe my current work is interesting. I am preparing a freeswitch package for buildroot[1] based on the FS master branch. My personal patch queue looks as follows: * fa1fe2b - package/freeswitch: new package (7 minutes ago) * a44ea0b - package/libsoundtouch: new package (7 minutes ago) * a123ec9 - package/libopenh264: new package (7 minutes ago) * f68a803 - package/libilbc: new package (7 minutes ago) * f404d8c - package/libg7221: new package (7 minutes ago) * f9db835 - package/libcodec2: new package (7 minutes ago) * 4d5d5a4 - package/libbroadvoice: new package (7 minutes ago) * 846e421 - package/libsilk: new package (7 minutes ago) * 1ad5ac0 - package/libyuv: new package (7 minutes ago) * 54dbe70 - package/libldns: new package (7 minutes ago) First question: Is there general interest in having freeswitch being committed to buildroot? This will ease the task of cross compiling. Second question: Currently I am using https://freeswitch.org/stash/projects/SD as source for the following libs: silk, g7221, codec2, soundtouch, broadvoice and ilbc. Should I continue to use the git repo as upstream source or is it a better idea to use the tarballs from http://files.freeswitch.org/downloads/libs/? When providing a package to the buildroot project I need to make sure that the upstream source is a valid source for the foreseeable future. Regards, Bernd [1] http://buildroot.uclibc.org/
Can you create a pull request for these please? William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.king@quentustech.com On 6/18/15 1:16 PM, Bernd Kuhls wrote:
Michael Jerris <mike@jerris.com> wrote in news:39F9F70C-6B5C-4F5D-9B49-7F08BDCB08E4@jerris.com:
--Apple-Mail=_703FC8B5-A831-4CD2-BE6F-9D24BE0DE535 For core freeswitch, likely yes. For the deps, someone will have to do the work and find out. I'd prefer to do this under cowbuilder along side how we build for all other platfroms, but someone will need to do the work to figure out what all exactly is necessary to make it happen.
On Jun 18, 2015, at 11:23 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Does cross-compiling work? Because building arm packages on an arm server takes about 6 hours.
Hi,
please excuse me if my posting is better suited for the -users mailinglist.
When it comes to cross compiling maybe my current work is interesting. I am preparing a freeswitch package for buildroot[1] based on the FS master branch. My personal patch queue looks as follows:
* fa1fe2b - package/freeswitch: new package (7 minutes ago) * a44ea0b - package/libsoundtouch: new package (7 minutes ago) * a123ec9 - package/libopenh264: new package (7 minutes ago) * f68a803 - package/libilbc: new package (7 minutes ago) * f404d8c - package/libg7221: new package (7 minutes ago) * f9db835 - package/libcodec2: new package (7 minutes ago) * 4d5d5a4 - package/libbroadvoice: new package (7 minutes ago) * 846e421 - package/libsilk: new package (7 minutes ago) * 1ad5ac0 - package/libyuv: new package (7 minutes ago) * 54dbe70 - package/libldns: new package (7 minutes ago)
First question: Is there general interest in having freeswitch being committed to buildroot? This will ease the task of cross compiling.
Second question: Currently I am using https://freeswitch.org/stash/projects/SD as source for the following libs: silk, g7221, codec2, soundtouch, broadvoice and ilbc. Should I continue to use the git repo as upstream source or is it a better idea to use the tarballs from http://files.freeswitch.org/downloads/libs/? When providing a package to the buildroot project I need to make sure that the upstream source is a valid source for the foreseeable future.
Regards, Bernd
[1] http://buildroot.uclibc.org/
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
William King <william.king@quentustech.com> wrote in news:5588A6A6.5000900@quentustech.com:
Can you create a pull request for these please?
On 6/18/15 1:16 PM, Bernd Kuhls wrote:
Second question: Currently I am using https://freeswitch.org/stash/projects/SD as source for the following libs: silk, g7221, codec2, soundtouch, broadvoice and ilbc. Should I continue to use the git repo as upstream source or is it a better idea to use the tarballs from http://files.freeswitch.org/downloads/libs/? When providing a package to the buildroot project I need to make sure that the upstream source is a valid source for the foreseeable future.
Hi, no problem after I received an answer to my second question ;) Regards, Bernd
Both would be fine, the tarballs are re-generated from the git source, so git is probably the easiest if the packaging system supports using git as the source. This is the general rule, in some cases you may have to do a bit more work. Some of these libraries we are the defacto upstream for, others we are just needing to rebuild against different versions of other libraries upstream, for example, we want to use libpng1.6 so we have transparent png support, which is required for some video features, and we require newer libvpx, these newer libs require us to relink libav with these newer libraries. If your distro already has suitable versions of these, this may not be necessary.
On Jun 25, 2015, at 1:28 PM, Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
William King <william.king@quentustech.com> wrote in news:5588A6A6.5000900@quentustech.com:
Can you create a pull request for these please?
On 6/18/15 1:16 PM, Bernd Kuhls wrote:
Second question: Currently I am using https://freeswitch.org/stash/projects/SD as source for the following libs: silk, g7221, codec2, soundtouch, broadvoice and ilbc. Should I continue to use the git repo as upstream source or is it a better idea to use the tarballs from http://files.freeswitch.org/downloads/libs/? When providing a package to the buildroot project I need to make sure that the upstream source is a valid source for the foreseeable future.
Hi,
no problem after I received an answer to my second question ;)
Regards, Bernd
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (3)
-
Bernd Kuhls
-
Michael Jerris
-
William King