Re: [Ekiga-devel-list] Win32 build of 3.0-trunk patched Makefile - WiP
Quoting Torsten Schlabach [EMAIL PROTECTED]: Hi all! Attached please find an interim patch for the win32/Makefile reflecting how far I got before I will have to call it a day for today. Please use in conjuction with http://wiki.ekiga.org/index.php/Cross-compile_Win32 This patch fixes the following: * automake and friends are recognized (1.9 / 1.10 issue) * the Ekiga source code is checked out directly via Subversion and no longer fatched from a snapshot which hasn't been updated since Nov 7th, 2007. (In other words, you think you're compiling the trunk version, but you don't until you use this patch * the x264 stuff is not fetched from their new git repository. We fetch the latest version always. The Makefile which went to the videolan svn was getting a specific release before. * I commented out some patches which do not seem to exist anymore On git: Never used this before. Right now when I run make update-sources for a 2nd time, it complains about the dir being there already. On commenting out patches: I run into some errors which I have seen on the native build of trunk for Linux. Probably these patches had some cross-compile specific stuff. Need to research. Therefore (see subject line) this patch will not yet make the build work again, but I want to share my current state. I hope I am moving in the right direction. Regards, Torsten Hi Torsten, first of all, thanks for the patches. I will revise the windows build taking into account your patches next weekend (sorry, this needs some time I do not have right now) You pull Ekiga directly from svn instead of downloading the tarball. That is a first start, but we have to do this for ptlib and opal as well, since the tarballs of them are really outdated. Also we do not want to rebuild all dependencies if nothing has changed after a checkout. I will thus need to modify your patch, which needs some time. Also you have commented out many lines where I do not understand that it still works at all, e.g. the compilation of ptlib... Last thing I would like to add is that we should either specify whether to use aclocal 1.9 or 1.10 in a single place or even autodetect this... 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
[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] 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-devel-list] Win32 build broken?
On Monday 10 March 2008 20:53:17 Torsten Schlabach wrote: --- Damien Sandras [EMAIL PROTECTED] schrieb: Is it trunk or 2.0.x ? I was going to say, it's trunk (as the filename has 'snapshot' in it), but: trunk=head=snapshot = soon-3.00 Well, one point is that the source code snapshot packages downloaded by the script are about 4 months old since Kilian does no longer maintain them (i.e. ptlib, opal and ekiga -snapshot). Ok, how about fixing that ... If you want to do that help is welcome in many areas of ekiga development and support. Second point is that even with current sources there is no guarantee that it will work since it has been a while since I last fixed it. The win32 build will be a major post-3.00 point. We'll know once we try. What I wonder, when you say Kilian does not longer maintain them, are these snapshot files more than just tared SVN snapshots? No they arent. You can replace these files by your own tarball and make use of the original makefile. Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list ___ 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 broken?
Le lundi 10 mars 2008 à 15:52 +0100, Torsten Schlabach a écrit : Dear list! I am currently trying this: http://wiki.ekiga.org/index.php/Cross-compile_Win32 but fail: # make make -j1 -C /usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib make[1]: Entering directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make all-am make[2]: Entering directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make[2]: *** No rule to make target `src/ptclib/url.cxx', needed by `url.lo'. Stop. make[2]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make: *** [/usr/local/src/ekiga-win32/ekiga-win32-cross/lib/libpt.a] Error 2 Is that anything obvious or should I work with the PTLib developers on that? They won't help with that, as it is a problem of cross-compilation. It seems to be indeed broken. You will have to fight with the Makefile to fix it or wait that somebody does it. -- _ 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 broken?
as it is a problem of cross-compilation. How can we be sure about that? Regards, Torsten Original-Nachricht Datum: Mon, 10 Mar 2008 15:57:09 +0100 Von: Damien Sandras [EMAIL PROTECTED] An: Ekiga development mailing list ekiga-devel-list@gnome.org Betreff: Re: [Ekiga-devel-list] Win32 build broken? Le lundi 10 mars 2008 à 15:52 +0100, Torsten Schlabach a écrit : Dear list! I am currently trying this: http://wiki.ekiga.org/index.php/Cross-compile_Win32 but fail: # make make -j1 -C /usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib make[1]: Entering directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make all-am make[2]: Entering directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make[2]: *** No rule to make target `src/ptclib/url.cxx', needed by `url.lo'. Stop. make[2]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross/ptlib' make: *** [/usr/local/src/ekiga-win32/ekiga-win32-cross/lib/libpt.a] Error 2 Is that anything obvious or should I work with the PTLib developers on that? They won't help with that, as it is a problem of cross-compilation. It seems to be indeed broken. You will have to fight with the Makefile to fix it or wait that somebody does it. -- _ 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 mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32 build broken?
Ok, I was able to get over that: # diff ptlib/Makefile.original ptlib/Makefile 305c305 am__objects_32 = url.lo --- #am__objects_32 = url.lo The source file url.cxx seems to have disappeared / been renamed. After commenting out that one line, I can successfully cross-compile ptlib. I seem go have an issue when it comes to installing: install: missing destination file operand after `/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/bin/avutil-49.5.0.dll' In context: make -C libavutil install-libs make[2]: Entering directory `/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/ffmpeg/libavutil' install -d /usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/bin install -m 755 /usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/bin/avutil-49.5.0.dll install: missing destination file operand after `/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/bin/avutil-49.5.0.dll' Try `install --help' for more information. make[2]: *** [install-lib-shared] Error 1 make[2]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/ffmpeg/libavutil' make[1]: *** [install-libs] Error 2 make[1]: Leaving directory `/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/ffmpeg' make: *** [/usr/local/src/ekiga-win32/ekiga-win32-cross2/ekiga-win32-cross/bin/avcodec.dll] Error 2 Regards, Torsten Original-Nachricht Datum: Mon, 10 Mar 2008 16:08:50 +0100 Von: Damien Sandras [EMAIL PROTECTED] An: Ekiga development mailing list ekiga-devel-list@gnome.org Betreff: Re: [Ekiga-devel-list] Win32 build broken? Le lundi 10 mars 2008 à 16:07 +0100, Torsten Schlabach a écrit : as it is a problem of cross-compilation. How can we be sure about that? Because the Makefiles are not the same in both cases. -- _ 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 mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Win32 build broken?
Le lundi 10 mars 2008 à 16:07 +0100, Torsten Schlabach a écrit : as it is a problem of cross-compilation. How can we be sure about that? Because the Makefiles are not the same in both cases. -- _ 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
Hi all, perhaps some of you have noticed that since 2 days ago no more windows snapshots have been created. This is due to a switch to mingw-gcc 4.2.1 (from 3.4.5) on the build -system. This is a good sign for our ugly ffmpeg-alignment problems we had been experiencing, rendering the h.263+ codec unusable, however, 4.2.1 is a lot stricter that previous versions, so it will need some effort to streamline our sources to get the windows build back on. Using gcc 4.2.1 on windows also means that finally we will be using the same compiler version for both windows and linux. Any help on bringing back the build will be appreciated. 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
[Ekiga-devel-list] WIN32?
Folks! - What's the status of the WIN32 installer? - Which version is the current GTK+ port? J. -- I know life sometimes can get tough! and I know life sometimes can be a drag! But people, we have been given a gift, we have been given a road And that roads name is... rock and roll! KISS in God gave Rock'n'Roll to you ___ 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
Hi, Thanks for your contribution! Le mardi 29 août 2006 à 14:40 +0200, Cedric Krier a écrit : Hi, Here is an nsi script to generate a setup.exe for ekiga on win32. To run it: # makensis ekiga.nsi I have put the different license for the dll's. I don't know if it is right. You can try the exe here : http://ced.homedns.org/Ekiga-setup.exe Cédric ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list -- _ Damien Sandras (o- //\ Ekiga Softphone: http://www.ekiga.org/ v_/_FOSDEM 2006: http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
