Re: [Ekiga-devel-list] SVN access for x264
Quoting Torsten Schlabach [EMAIL PROTECTED]: sean darcy schrieb: Just to keep everyone on their toes, x264 has closed the svn repo, and is using git. Try: git clone git://git.videolan.org/x264.git and git pull --rebase = svn update For building releases of Ekiga (e.g. 2.0.12 for example), did the x264 guys migrate the SVN history to git or would there by any downloadable tarballs of older versions? What version of x264 does 2.0.12 or the recent Gnome branch rely on? Using the above, you'll always get the latest. For the Debian users among us: Make sure you install git-core, not git. The package called git in Debian Etch is not what you think it is. Regards, Torsten Hi Torsten, like stated by Yannick x264 changed to git. I have updated the Ekiga wiki on this issue. By the way, you have been asking about the win32 build... Since you have been putting some effort into this, may I ask if you would like to work with the win32 build once it is functional? I could fix it to compile within the next week, but I will only spend the extra effort needed if someone will acutally be using the build. It is always a moving target to keep it up-to-date to current opal, ptlib and ekiga, so I have preferred to put resources into something more productive in the last months... Matthias This message was sent using IMP, the Internet Messaging Program. ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] SVN access for x264
Le lundi 31 mars 2008 à 15:19 +0200, Matthias Schneider a écrit : Quoting Torsten Schlabach [EMAIL PROTECTED]: sean darcy schrieb: Just to keep everyone on their toes, x264 has closed the svn repo, and is using git. Try: git clone git://git.videolan.org/x264.git and git pull --rebase = svn update For building releases of Ekiga (e.g. 2.0.12 for example), did the x264 guys migrate the SVN history to git or would there by any downloadable tarballs of older versions? What version of x264 does 2.0.12 or the recent Gnome branch rely on? Using the above, you'll always get the latest. For the Debian users among us: Make sure you install git-core, not git. The package called git in Debian Etch is not what you think it is. Regards, Torsten Hi Torsten, like stated by Yannick x264 changed to git. I have updated the Ekiga wiki on this issue. By the way, you have been asking about the win32 build... Since you have been putting some effort into this, may I ask if you would like to work with the win32 build once it is functional? I could fix it to compile within the next week, but I will only spend the extra effort needed if someone will acutally be using the build. It is always a moving target to keep it up-to-date to current opal, ptlib and ekiga, so I have preferred to put resources into something more productive in the last months... I spoke with Craig (from OPAL), and it seems he could be the next one to maintain the WIN32 build. He is currently trying to cross-compile and see what he can do to help. However, I do not think Craig alone has enough spare time to code missing pieces in the WIN32 build. So if we can get several people making it rock, it is worth it. I'm just not a WIN32 developer :( -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] SVN access for x264
Hi Matthias! By the way, you have been asking about the win32 build... Since you have been putting some effort into this, may I ask if you would like to work with the win32 build once it is functional? I could fix it to compile within the next week, but I will only spend the extra effort needed if someone will acutally be using the build. I suggest we create a new thread for that discussion. Last night I was at about 99% (I think ... I hope) to build 2.0.11 for Windows myself for the 1st time. I am about to re-produce and document. Well, as said ... Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] SVN access for x264
Quoting Damien Sandras [EMAIL PROTECTED]: Le lundi 31 mars 2008 à 15:19 +0200, Matthias Schneider a écrit : Quoting Torsten Schlabach [EMAIL PROTECTED]: sean darcy schrieb: Just to keep everyone on their toes, x264 has closed the svn repo, and is using git. Try: git clone git://git.videolan.org/x264.git and git pull --rebase = svn update For building releases of Ekiga (e.g. 2.0.12 for example), did the x264 guys migrate the SVN history to git or would there by any downloadable tarballs of older versions? What version of x264 does 2.0.12 or the recent Gnome branch rely on? Using the above, you'll always get the latest. For the Debian users among us: Make sure you install git-core, not git. The package called git in Debian Etch is not what you think it is. Regards, Torsten Hi Torsten, like stated by Yannick x264 changed to git. I have updated the Ekiga wiki on this issue. By the way, you have been asking about the win32 build... Since you have been putting some effort into this, may I ask if you would like to work with the win32 build once it is functional? I could fix it to compile within the next week, but I will only spend the extra effort needed if someone will acutally be using the build. It is always a moving target to keep it up-to-date to current opal, ptlib and ekiga, so I have preferred to put resources into something more productive in the last months... I spoke with Craig (from OPAL), and it seems he could be the next one to maintain the WIN32 build. He is currently trying to cross-compile and see what he can do to help. However, I do not think Craig alone has enough spare time to code missing pieces in the WIN32 build. So if we can get several people making it rock, it is worth it. I'm just not a WIN32 developer :( In that case I will try to fix it as soon as possible, i.e. probably next weekend... Matthias This message was sent using IMP, the Internet Messaging Program. ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] SVN access for x264
Le lundi 31 mars 2008 à 15:51 +0200, Matthias Schneider a écrit : Quoting Damien Sandras [EMAIL PROTECTED]: Le lundi 31 mars 2008 à 15:19 +0200, Matthias Schneider a écrit : Quoting Torsten Schlabach [EMAIL PROTECTED]: sean darcy schrieb: Just to keep everyone on their toes, x264 has closed the svn repo, and is using git. Try: git clone git://git.videolan.org/x264.git and git pull --rebase = svn update For building releases of Ekiga (e.g. 2.0.12 for example), did the x264 guys migrate the SVN history to git or would there by any downloadable tarballs of older versions? What version of x264 does 2.0.12 or the recent Gnome branch rely on? Using the above, you'll always get the latest. For the Debian users among us: Make sure you install git-core, not git. The package called git in Debian Etch is not what you think it is. Regards, Torsten Hi Torsten, like stated by Yannick x264 changed to git. I have updated the Ekiga wiki on this issue. By the way, you have been asking about the win32 build... Since you have been putting some effort into this, may I ask if you would like to work with the win32 build once it is functional? I could fix it to compile within the next week, but I will only spend the extra effort needed if someone will acutally be using the build. It is always a moving target to keep it up-to-date to current opal, ptlib and ekiga, so I have preferred to put resources into something more productive in the last months... I spoke with Craig (from OPAL), and it seems he could be the next one to maintain the WIN32 build. He is currently trying to cross-compile and see what he can do to help. However, I do not think Craig alone has enough spare time to code missing pieces in the WIN32 build. So if we can get several people making it rock, it is worth it. I'm just not a WIN32 developer :( In that case I will try to fix it as soon as possible, i.e. probably next weekend... Thanks Matthias! -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Win32 build and continuous integration
Hi all! Just to make sure we will ever find this thread again in the archive. Some of you may have noticed that I spent some time trying to get my hands around the Win32 build of Ekiga. You can find my notes in the Wiki. I am not sure if I am just too stupid, but this is a bit like an advent calendar: There's a surprise behind every door your open. After having spent a couple of nights on the subject I was a bit suprised by some people on this list coming up like: You want me to fix this? No problem! Well, if it's that easy, please go ahead. All I would like to see is a concise guide like: - Take a plain XYZ machine. - Install a, b and c. - Issues these commands. - Enjoy. It's a bit difficult to find the point to start, as there are three versions that one could try: - 2.0.11 (there has been a Windows build for it once) - 2.0.12 has different compile failures than 2.0.11 on an identical box - trunk (is a moving target anyway, not just for the cross build) So what would indeed make a difference would be - besides a repeatable process - to get back to automated daily snapshot builds, so that if anything either in Ekiga itself or in the outside world (dependencies) changes, we will notice right in time that the build is broken and act. I think a working build (at least once; I am trying for days and nights without a single success with either version) would be a starting point, but once we will have that, by whoever efforts, what would need to get done to get daily automated builds again? Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] patches for OPAL for FreeBSD
Le lundi 31 mars 2008 à 19:52 +0200, Matthias Schneider a écrit : Quoting Damien Sandras [EMAIL PROTECTED]: Hi Matthias, Le vendredi 28 mars 2008 à 07:36 +0100, Matthias Apitz a écrit : Hi Damien, I'm attaching some small patches for OPAL to make it working in FreeBSD; some pieces are #if defined P_FREEBSD wrapped and should cause no problem in other systems; concerning the 'configure' changes I don't know how to provide a common solution (_dlopen friends are just in libc.so) because 'configure' and 'plugins/configure' are generated, but in SVN; please check what you could do so a 'svn update' will not clobber my changes in my local rep. :-) I have committed the parts of the patch I thought relevant. I did not commit : * the patch done on configure instead of configure.ac * the patch redefining the path for FreeBSD (/usr/local/lib/ptlib should be added to the Unix path next to /usr/lib/ptlib, but I can not test) Thanks! I have a question about the commit in trace.cxx: I found out that there is a basename defined in both string.h and libgen.h. However I would prefer to use the string.h-basename. Matthias, could you try a simple #include string.h instead of the #ifdef P_FREEBSD #include libgen.h #endif ? I would rather use the same basename on all platforms, and the string.h can be used on linux as well (it seems to be used implicitly here) If it works, it is indeed better to use string.h (and probably not use @ifdef P_FREEBSD -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32 build and continuous integration
Hi, Le lundi 31 mars 2008 à 16:25 +0200, Torsten Schlabach a écrit : Hi all! Just to make sure we will ever find this thread again in the archive. Some of you may have noticed that I spent some time trying to get my hands around the Win32 build of Ekiga. You can find my notes in the Wiki. I am not sure if I am just too stupid, but this is a bit like an advent calendar: There's a surprise behind every door your open. After having spent a couple of nights on the subject I was a bit suprised by some people on this list coming up like: You want me to fix this? No problem! Well, if it's that easy, please go ahead. All I would like to see is a concise guide like: - Take a plain XYZ machine. - Install a, b and c. - Issues these commands. - Enjoy. There is a start in the wiki, but it is probably not complete enough :( It's a bit difficult to find the point to start, as there are three versions that one could try: - 2.0.11 (there has been a Windows build for it once) - 2.0.12 has different compile failures than 2.0.11 on an identical box Which is weird because the sources only slightly change. - trunk (is a moving target anyway, not just for the cross build) It is also the future of Ekiga. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Win32-Build: Success except installer!
Hi all! To report someting positive in between. The cross-build for Win32 creates an .exe file which works. Just the installer generation is pretty broken. But with that state, at least I will be able to make code changes (i.e. fix a specific bug which bugs me), run the build, copy the .exe to my Windows box and test. I am inviting anyone who's interested to challenge my writeup at http://wiki.ekiga.org/index.php/Cross-compile_Win32 I have been using a Debian Lenny system and Ekiga 2.0.11; the last one which was known to cross-build for Windows at all. Starting from a minimal system (debootstrap) I 1. installed the dependencies as per the headline Compile Time (host) Dependencies 2. Downloaded the source tarball from http://www.ekiga.org/admin/downloads/2.0.11/sources/sources/ekiga-2.0.11.tar.gz. (That URL is not linked anywhere, I was guessing it.) 3. Patched the Makefile with a %s/-1.9/-1.10/g in vi to solve the problem that version 1.10 of the autotools isn't properly recognized. (I think this is a Debian bug, not sure.) 4. Patched the Makefile with a new URL for EXPAT: http://heanet.dl.sourceforge.net/sourceforge/expat 5. Applied this patch: http://bugs.gentoo.org/show_bug.cgi?id=195227 I'd hope this makes it for an make update-sources make up to the point where it should complain about some nsis stuff. You can then take the ekiga.exe file and replace it in an existing installation. By the way: I wanted to give 2.0.11-BETA to someone recently, but wasn't able to find any download link anymore ... So obviously, there's quite a TODO list remaining, including - re-testing my instructions - having some bugs in upstream stuff fixed - making all of this work on a Debian Etch system, as Lenny is just a snapshot and nobody knows if this will work in some weeks from now. But that will probably involve a backport of mingw32 stuff for Etch. - fixing the installer generation - trying all this with 2.0.12 and 3.0 Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32 build and continuous integration
Hi! Damien Sandras schrieb: All I would like to see is a concise guide like: - Take a plain XYZ machine. - Install a, b and c. - Issues these commands. - Enjoy. There is a start in the wiki, but it is probably not complete enough :( IMO the problem with any guide is assumptions. Anyone who's writing such guides silently assumes that the reader will work in a similar environment, will have similar tools installed and will approach tasks in a similar way. The more skilled someone is in writing guides, the more the writer will think with the reader and make such assumptions explicit. That will at least provide the reader with heads-up if something is different on his system than what the writer assumes. But on the other hand, IMO, it cannot be the answer to have detailled guides for any flavor of Linux how to cross-compile Ekiga. That would just be the next maintainance nightmare. If we keep guides for Debian, Ubuntu, Red Hat and SuSE and Gentoo (apologies if I missed your favorite distro) and we'd have a change like the SVN - git move of x264 we would need to update 5 different guides. So what I wonder is if there aren't any more intelligent mechanisms to handle such a cross-build and make it more robust across different distributions or at least make dependencies and potential problems which they cause a bit more transparent. I mean, is Ekiga the first cross-platform open source project? How do other people (Mozilla, eMule, [your favorite cross-platform OSS app]) handle this? Besides that, what I would like to understand: What would it take to get an automated daily snapshot build of Ekiga back? Why isn't it available anymore? Is that just because it stopped working, therefore someone switched it off or did the infrastructure for that snapshot build disappear? If the infrastructure was still available: What does it look like? What flavor of Linux? What version? How is the daily build performed? Is it a script? Is the whole server rebuilt nightly from scratch, ...? Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32-Build: Success except installer!
Le lundi 31 mars 2008 à 21:11 +0200, Torsten Schlabach a écrit : Hi all! To report someting positive in between. The cross-build for Win32 creates an .exe file which works. Just the installer generation is pretty broken. But with that state, at least I will be able to make code changes (i.e. fix a specific bug which bugs me), run the build, copy the .exe to my Windows box and test. I am inviting anyone who's interested to challenge my writeup at http://wiki.ekiga.org/index.php/Cross-compile_Win32 I have been using a Debian Lenny system and Ekiga 2.0.11; the last one which was known to cross-build for Windows at all. Starting from a minimal system (debootstrap) I 1. installed the dependencies as per the headline Compile Time (host) Dependencies 2. Downloaded the source tarball from http://www.ekiga.org/admin/downloads/2.0.11/sources/sources/ekiga-2.0.11.tar.gz. (That URL is not linked anywhere, I was guessing it.) 3. Patched the Makefile with a %s/-1.9/-1.10/g in vi to solve the problem that version 1.10 of the autotools isn't properly recognized. (I think this is a Debian bug, not sure.) 4. Patched the Makefile with a new URL for EXPAT: http://heanet.dl.sourceforge.net/sourceforge/expat 5. Applied this patch: http://bugs.gentoo.org/show_bug.cgi?id=195227 I'd hope this makes it for an make update-sources make up to the point where it should complain about some nsis stuff. You can then take the ekiga.exe file and replace it in an existing installation. By the way: I wanted to give 2.0.11-BETA to someone recently, but wasn't able to find any download link anymore ... So obviously, there's quite a TODO list remaining, including - re-testing my instructions - having some bugs in upstream stuff fixed - making all of this work on a Debian Etch system, as Lenny is just a snapshot and nobody knows if this will work in some weeks from now. But that will probably involve a backport of mingw32 stuff for Etch. - fixing the installer generation - trying all this with 2.0.12 and 3.0 2.0.x being relatively dead, I would concentrate my efforts on 3.0. Great job btw! -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-list] Ekiga vs Skype
I'm almost sure the problem is this: http://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 http://pulseaudio.org/ticket/23 https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/112948 Regards, Yannick I reported to bugtrack that the patch for report 2601 does not fix the crash I report, nor does it remove the assert error I am getting. Dee _ In a rush? Get real-time answers with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_realtime_042008___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] eeepc
Unfortunately, I do not think the problem is at our level... Have you tried contacting eeepc developers? They could have a look (or send one to us so we can fix it). Now that's a good idea! I'll let you know if I have any luck Thanks - Sent from Yahoo! Mail. A Smarter Inbox.___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga vs Skype
Hello Dee, On Mon, Mar 31, 2008 at 2:32 AM, D Webb [EMAIL PROTECTED] wrote: I'm almost sure the problem is this: http://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 http://pulseaudio.org/ticket/23 https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/112948 Regards, Yannick I reported to bugtrack that the patch for report 2601 does not fix the crash I report, nor does it remove the assert error I am getting. I don't know wheather you saw the report I gave, but when I removed PulseVideo from my system, it corrected my problem. At least testing with 500, but have not tested with another user. Peaceed -- Edward Dunagin-Dunigan Bozeman, MT 59718 mobile 406-570-0992 Landline 406-556-7282 VOIP:sip:[EMAIL PROTECTED] http://doas.montanalinux.org ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
