Re: [Ekiga-devel-list] win32 build updated
Quoting Matthias Schneider [EMAIL PROTECTED]: Quoting Damien Sandras [EMAIL PROTECTED]: Le mardi 08 avril 2008 à 17:30 +0200, Torsten Schlabach a écrit : Damien Sandras wrote: I only host ekiga.org/ekiga.net and mirror the result of the build done by Kilian on another machine (which is not maintained anymore). What's not maintained anymore? The machine or the build? Both I suppose. Does anyone except Kilian have access to that machine? No. Would Kilian grant anyone else access to that machine? I dont know. Kilian ?? (in CC, if he answers) In case the answer to both questions was no: If I had a machine (I do, actually) what would it take to make a nightly build happen and mirror it? Don't get me wrong: If Kilian would be so nice, I think this would be the most efficient way. In case he doesn't or cannot help anymore, the question would be if we could at least re-use any scripts from the old box. Kilian, can you enlighten us ? -- _ Damien Sandras Torsten, my NSIS: makensis -VERSION v2.33-1 I am running debian unstable. It seems the build setup is still set up, you can see the logs at http://trinity.buildserver.net/~kk/ekiga_win32_crosscompile.log As far as I know once a file is generated, it should go to http://archive.buildserver.net/win32/ However since there seems to be some manual interaction needed on the build machine I do not know if we can get it up without Kilian... Matthias Hi Torsten, it has been suspected by Robert that the wchar issue in ptlib and opal may be due to the following section in ptlib/include/ptlib/pstring.h: 50 #if (defined(_WIN32) || defined(_WIN32_WCE)) (!defined(_NATIVE_WCHAR_T_DEFINED)) 51 PBASEARRAY(PWCharArray, unsigned short); 52 #else 53 PBASEARRAY(PWCharArray, wchar_t); 54 #endif Maybe you would like to investigate further? Maybe all that is needed is a fixed #if? 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] win32 build updated
Hi Matthias! Regarding the installer: I commented out all lines saying SetBrandingImage in my /usr/share/nsis/Contrib/Modern\ UI/System.nsh file. This got me beyond that Error: no branding image found in chosen UI! Error in macro MUI_HEADERIMAGE_INIT on macroline 27 [...] Error in macro MUI_LANGUAGE on macroline 7 Error in script /usr/local/src/ekiga-win32/nsisinstaller/ekiga.nsi on line 107 -- aborting creation process make: *** [/usr/local/src/ekiga-win32/dist/ekiga-setup-2.9.exe] Error 1 The makensis is currently breaking like this: Goto: ekiga_install_files ReadRegStr $R1 HKLM\SOFTWARE\GTK\2.0\Path SetOutPath: $INSTDIR SetOverwrite: on File: ekiga.exe [compress]Bus error That Bus error might be something on my machine. I keep searching. Regards, Torsten Original-Nachricht Datum: Tue, 08 Apr 2008 10:57:18 +0200 Von: Matthias Schneider [EMAIL PROTECTED] An: Torsten Schlabach [EMAIL PROTECTED] CC: ekiga-devel-list@gnome.org Betreff: Re: [Ekiga-devel-list] win32 build updated Quoting Torsten Schlabach [EMAIL PROTECTED]: Good morning! 1. There is still that automake-1.9 versus 1.20 problem. I had to patch the Makefile. Yes, but just in 1 place and no longer in 4 places. In case you have an idea how to autodetect this, feel free to contribute. Not yet, but I am sure, we will find something. Some gnome config script has the same problem and they haven't solved that yet AFAIK. It's prio #2 for me, right *after* being able to actually run a 3.0 SVN on Windows (see installer issue). Yes, I concur... - Will we now have a nightly build again? It seems the infrastructure is still up. That means once pptlib and opal build out of the box again, we probably will. If the infrastructure is not up anymore, probably not... I would be able to donate infrastructure if needed. Who owns the current one? Hm, is it Kilian's? Damien? I can check tonight if it still works... [2.0 build] What do you mean keep it around? I thought its not working anyway? I can only tell you I do not have a single minute I can put into anything related to 2.0.x, actually I had mentally moved the 3.0 windows buidl to 3.2 already... I mean: Keep the Wiki page where it is and accept a fix to the Makefile if I or someone else has one. I am supporting people who use 2.0.11 on Windows right now. They have some issues which I might need to fix or which might be fixed already in 2.0.12. But I cannot move these people to a moving target 3.0 SVN version. Isn't it good practice to keep bugfixing the stable version of an app until the next version is out and usually even running for X amount of time? I can understand that you cannot / don't want to spent time on it, but others might want to. If possible, I'd like to avoid the situation where 2.0 doesn't work and 3.0 isn't there yet. You are right that this should be the way to go. In case you want to contribute to both 2.x and 3.0 for windows this would be very appreciated. I also did not know that there are people actually using Ekiga for win since it was never officially released... However, like I said before I can give you support only on the 3.0 version. About 3.0, one known issue is that the DirectShow plugin does not seem to be linked correctly anymore since the switch to gcc 4.x. Any hint on that would also be very appreciated (provided ekiga runs at all, which I havent tried for months...) About the installer, I have no idea right now except that I will compare your nsis version with mine... Which one do you have? On what distro? I cannot check before tonight... Regards, Torsten Matthias Original-Nachricht Datum: Tue, 08 Apr 2008 08:41:36 +0200 Von: Matthias Schneider [EMAIL PROTECTED] An: Ekiga development mailing list ekiga-devel-list@gnome.org, Torsten Schlabach [EMAIL PROTECTED] CC: Ekiga development mailing list ekiga-devel-list@gnome.org Betreff: Re: [Ekiga-devel-list] win32 build updated Quoting Torsten Schlabach [EMAIL PROTECTED]: Hi Matthias! Thanks for your effort. I couldn't wait to try it. Good news first: It worked 99%! It compiled Ekiga, but it failed to create the installer. I will attach a complete log file of the entire build. Some remarks: 1. There is still that automake-1.9 versus 1.20 problem. I had to patch the Makefile. Yes, but just in 1 place and no longer in 4 places. In case you have an idea how to autodetect this, feel free to contribute. 2. It seems to be important to stick to 1. make update-sources 2. apply the patches to OPAL and PTLib (as long as they are needed) 3. make In an earlier attempt, I was curious if I would get the same error message which you got, so I did not patch, but did a make update-sources, tried
Re: [Ekiga-devel-list] win32 build updated
Le mardi 08 avril 2008 à 10:57 +0200, Matthias Schneider a écrit : Hm, is it Kilian's? Damien? I can check tonight if it still works... Hi, It's Kilian's. [2.0 build] What do you mean keep it around? I thought its not working anyway? I can only tell you I do not have a single minute I can put into anything related to 2.0.x, actually I had mentally moved the 3.0 windows buidl to 3.2 already... I mean: Keep the Wiki page where it is and accept a fix to the Makefile if I or someone else has one. I am supporting people who use 2.0.11 on Windows right now. They have some issues which I might need to fix or which might be fixed already in 2.0.12. But I cannot move these people to a moving target 3.0 SVN version. Isn't it good practice to keep bugfixing the stable version of an app until the next version is out and usually even running for X amount of time? I can understand that you cannot / don't want to spent time on it, but others might want to. If possible, I'd like to avoid the situation where 2.0 doesn't work and 3.0 isn't there yet. You are right that this should be the way to go. In case you want to contribute to both 2.x and 3.0 for windows this would be very appreciated. I also did not know that there are people actually using Ekiga for win since it was never officially released... However, like I said before I can give you support only on the 3.0 version. At the time we did packaged 2.0.9 for windows there was people using it on ekiga.net (as it showed up first in the white pages). I think it should be some today. Probably TheBonsai could tell how much (asking SER). Regards, Yannick -- Me joindre en téléphonie IP / vidéoconférence ? sip:[EMAIL PROTECTED] Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F ___ 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 updated
Le mardi 08 avril 2008 à 16:45 +0200, yannick a écrit : Le mardi 08 avril 2008 à 10:57 +0200, Matthias Schneider a écrit : Hm, is it Kilian's? Damien? I can check tonight if it still works... Hi, It's Kilian's. I only host ekiga.org/ekiga.net and mirror the result of the build done by Kilian on another machine (which is not maintained anymore). -- _ 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 updated
Damien Sandras wrote: I only host ekiga.org/ekiga.net and mirror the result of the build done by Kilian on another machine (which is not maintained anymore). What's not maintained anymore? The machine or the build? Does anyone except Kilian have access to that machine? Would Kilian grant anyone else access to that machine? In case the answer to both questions was no: If I had a machine (I do, actually) what would it take to make a nightly build happen and mirror it? Don't get me wrong: If Kilian would be so nice, I think this would be the most efficient way. In case he doesn't or cannot help anymore, the question would be if we could at least re-use any scripts from the old box. Regards, Torsten ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
