Re: [Ekiga-list] Compiling ptlib-2.10.1 for Ekiga 3.3.1
Hi Antonio, On Sun, Jul 17, 2011 at 12:32:09PM +0200, Antonio Trande wrote: Compiling lastest ptlib-2.10.1, after *./configure command *i've got this output: $ make make/ptlib.mak:43: /home/ken/Compiled: No such file or directory make/ptlib.mak:43: Software/ptlib-2.10.1/make/unix.mak: No such file or directory make/ptlib.mak:44: /home/ken/Compiled: No such file or directory make/ptlib.mak:44: Software/ptlib-2.10.1/make/common.mak: No such file or directory make: *** No rule to make target `Software/ptlib-2.10.1/make/common.mak'. Stop. that's obviously a missing quoting of the path for ptlib sources. Try using a directory other than /home/ken/Compiled Software/ptlib-2.10.1 without white space in the name. -- Best regards, Kilian signature.asc Description: Digital signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-devel-list] dump audio video at real time
Hi Carlos, On Tue, Oct 09, 2007 at 03:50:26AM -0400, Carlos Hernandez wrote: is it posible to send the video and the audio to separated file using ekiga?, (may be opal). I mean, what I want is to save raw video and audio to the hard drive while a call is established. using wireshark and the rtpplay module from OPAL samples should do the trick at least for audio, not sure it can playback video. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Useless shared linked libs in Ekiga 2.0.11
Hi Julien, On Sun, Oct 07, 2007 at 11:34:48AM +0200, Julien Puydt wrote: Kilian Krause a écrit : At a first glance this is due to configure demanding these to be added to LDFLAGS. If someone finds the time to go through these and strip it down to only the required ones before me, please feel free to do so. Isn't it pkg-config adding them? In that case, we can hardly do anything... sadly it looks like this is a pkg-config issue of those packs. The question is whether we should work around this locally for now or just start feedking them the information.. I'll try to compile a list which of the packs does report which of those libs incorrectly. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Useless shared linked libs in Ekiga 2.0.11
Hi guys, as the new dpkg does chatter a bit more about useful and not so useful depends declared by linking libraries that in fact aren't used, I can herewith present you with the output of the latest 2.0.11 release build: full build uselessly linked with: libaudiofile.so.0 (it uses none of its symbols). libSM.so.6 (it uses none of its symbols). libICE.so.6 (it uses none of its symbols). libbonoboui-2.so.0 (it uses none of its symbols). libgnomevfs-2.so.0 (it uses none of its symbols). libgnomecanvas-2.so.0 (it uses none of its symbols). libart_lgpl_2.so.2 (it uses none of its symbols). libatk-1.0.so.0 (it uses none of its symbols). libpangocairo-1.0.so.0 (it uses none of its symbols). libfontconfig.so.1 (it uses none of its symbols). libXext.so.6 (it uses none of its symbols). libXrender.so.1 (it uses none of its symbols). libXinerama.so.1 (it uses none of its symbols). libXi.so.6 (it uses none of its symbols). libXrandr.so.2 (it uses none of its symbols). libXcursor.so.1 (it uses none of its symbols). libXcomposite.so.1 (it uses none of its symbols). libXdamage.so.1 (it uses none of its symbols). libcairo.so.2 (it uses none of its symbols). libXfixes.so.3 (it uses none of its symbols). libpopt.so.0 (it uses none of its symbols). libxml2.so.2 (it uses none of its symbols). libgmodule-2.0.so.0 (it uses none of its symbols). librt.so.1 (it uses none of its symbols). libdl.so.2 (it uses none of its symbols). libpthread.so.0 (it uses none of its symbols). libgcc_s.so.1 (it uses none of its symbols). --disable-gnome variant uselessly linked with: libatk-1.0.so.0 (it uses none of its symbols). libpangocairo-1.0.so.0 (it uses none of its symbols). libfontconfig.so.1 (it uses none of its symbols). libXext.so.6 (it uses none of its symbols). libXrender.so.1 (it uses none of its symbols). libXinerama.so.1 (it uses none of its symbols). libXi.so.6 (it uses none of its symbols). libXrandr.so.2 (it uses none of its symbols). libXcursor.so.1 (it uses none of its symbols). libXcomposite.so.1 (it uses none of its symbols). libXdamage.so.1 (it uses none of its symbols). libcairo.so.2 (it uses none of its symbols). libXfixes.so.3 (it uses none of its symbols). libgmodule-2.0.so.0 (it uses none of its symbols). librt.so.1 (it uses none of its symbols). libxml2.so.2 (it uses none of its symbols). libdl.so.2 (it uses none of its symbols). libpthread.so.0 (it uses none of its symbols). libgcc_s.so.1 (it uses none of its symbols). At a first glance this is due to configure demanding these to be added to LDFLAGS. If someone finds the time to go through these and strip it down to only the required ones before me, please feel free to do so. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] *.dll entry in Makefile
Hi Swen, On Sun, Sep 23, 2007 at 07:40:23PM +0200, Swen Walkowski wrote: Sorry to interrupt you again, but I need your help again. I have written a *.dll for my functionality witch I will try to do with the image. That I don't have to recompile Ekiga all the time, I want to use a library. I have done a littel change in the 'videoinput.cpp'. After that I have copied my libVideoAR.dll to the Linux PC, in the folder 'win32/lib/'. I need the library functionality in the 'videoinput'. So where I have to do the changes in the Makefile? I have tried the changes in the Makefile in the directory 'win32/eliga/src/Makefile'. In the line 767 and the following, from the current 'trunk'. But the reference is doesn't found. Error: videoinput.o: In function `_ZN14GMVideoGrabber4MainEv': /home/pfefferkeks/win32/ekiga/src/devices/videoinput.cpp:125: undefined reference to `Transport_Ekiga_AR::getInstance()' you can try tweaking the line $(MAKE) $(MAKEOPTS) -C $(EKIGA_DIR) in win32/Makefile and put CFLAGS or CXXFLAGS there. Otherwise you'll need to fiddle the -lVideoAR into the CFLAGS or CXXFLAGS into the ekiga Makefiles themselves. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] *.dll entry in Makefile
Hi Swen, On Sun, Sep 23, 2007 at 10:21:15PM +0200, Swen Walkowski wrote: Hi Kilian, Kilian Krause schrieb: you can try tweaking the line $(MAKE) $(MAKEOPTS) -C $(EKIGA_DIR) in win32/Makefile and put CFLAGS or CXXFLAGS there. Otherwise you'll need to fiddle the -lVideoAR into the CFLAGS or CXXFLAGS into the ekiga Makefiles themselves. I have tried in the ekiga Makefile (win32/ekiga/Makefile): CFLAGS = -I/home/pfefferkeks/win32/include -lVideo_Conference_AR -march=pentium-mmx -DPTRACING and the same for CXXFLAGS, but with out any success. Also I have tried to use CFLAGS and/or CXXFLAGS in the line $(MAKE) $(MAKEOPTS) -C $(EKIGA_DIR) Always the same result: videoinput.o: In function `_ZN14GMVideoGrabber4MainEv': /home/pfefferkeks/win32/ekiga/src/devices/videoinput.cpp:125: undefined reference to `Transport_Ekiga_AR::getInstance()' /home/pfefferkeks/win32/ekiga/src/devices/videoinput.cpp:125: undefined reference to `Transport_Ekiga_AR::extendImageAR(unsigned char const*, unsigned int, unsigned int)' The library lies under 'win32/lib' with the name 'libVideo_Conference_AR.dll' (I have had to change the name from libVideoAR). Also I have tired 'libVideo_Conference_AR.dll.a' By the way the *.dll file is done with VS2008, is that an problem? Nope, shouldn't be a problem. You may need -L/home/pfefferkeks/win32/lib additionally to -lVideo_Conference_AR ... -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Compile gnome-2-20 (last stable) for Win32
Hi Swen, [EMAIL PROTECTED]:~/win32$ make /bin/sh: line 0: cd: /home/pfefferkeks/win32/ekiga-/home/pfefferkeks/win32: No such file or directory what you obviously see is ekiga- which is entirely lacking the version but instead suffixing the entire local path. That apparently is an issue with BUILDROOT. As said, the old idea was to run make in the toplevel dir to ekiga itself. This was changed and the makefile from the SVN branch tries to find ekiga-X.Y.Z in the path and poke around. Just move the gnome-2-20 dir to be named ekiga-2.0.x and it'll work.o You'll need to manually create include/, lib/ and src/ at the same level as ekiga-* .. That'll mean you have: win32/ - lib/ - src/ - include/ - ekiga-2.0.x/ - win32/ ... and in that win32/ dir you just type make. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga-snapshot Debian package
Ciao Luca, Kilian, I think that libopal-cvs should now also suggests libx264-54! yes. Added. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] cvs voxgratia snapshot stale
Hi Anand, On Thu, Aug 16, 2007 at 10:28:21AM -0500, Anand R. Setlur wrote: The voxgratia cvs snapshot does not look as current as the buildserver.net cvs snapshot. Any reason why they are not mirroring each other? fixed. Thanks for spotting this. -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] VoIP IPv6 projects for presentation at ECAI6?
Hi all, as you may already have spotted I'll be doing a 45min talk at ECAI6 (European Conference on Applied IPv6 - http://www.guug.de/veranstaltungen/ecai6-2007/) about how to use VoIP over IPv6. Surely some of you have very interesting projects in this area, so please feel free to drop me a note with a heads up what you've been doing. The final presentation is due August 12, thus it'd be great if I had your feedback before then. Of course I hope to have a working IPv6-ready Ekiga by then to not need to present GnomeMeeting for IPv6-capable VoIP. If there's anything I can help with it, please let me know! -- Cheers! Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Improving the GNOME experience : request for help
Hi David, first, sorry for the delay. I thought I should take my time to get the answers more comprehensible, but I guess before this will not get answered at all, I'll just jumpstart and whoever thinks it's not clear enough, please bug me with questions. ;) 5) Build a repository What are the issues with the existing repositories? The existing repositories will be built from the repository the release maintainer will build. Currently, each time I receive a package, I need to scp it to ekiga.org. That is time consuming for me. Every release, I loose a few hours on that instead of coding. Could a release manager extend the script that builds the nightly snapshots to also make release packages? Does the build script automatically slurp the library tarballs or CVS down from Sourceforge? I don't really know, Kilian is handling that script, he is in CC. Notice you will have to use specific branches and tags, so the script should be made generic. You do not need to build on all distributions, you just need to create the tarballs and test. Well, the problem with release packs is not really with packaging, but with Craig and the official tarballs on voxgratia.org. These tarballs should be well tested (as is the case with CVS snaps already), so we might want to introduce an extra snapshots part for the other branches. For this, my current script doesn't scale too well, but I'm willing to put it onto public webspace for review. As the generation of package sources is done outside in an extra script anyway, this will scale pretty nicely once the checkout script can do more than one branch. The main problem with this is that the config should reside in the SVN/CVS of the project, so that upstream maintainers can choose the mappings. For this we'd need to put up a map like: HEAD = ekiga-snapshots gnome-2-18 = ekiga-2-18 etc. From there the question is how to handle the library dependencies with these snapshots. For example HEAD can be built with HEAD libs, but gnome-2-18 should be built with Phobos or some other branch. If you can come up with a scheme that can do this kind of mapping in a flexible and scalable config (so that my script will be able to read it and make packs non-interactively), I'll be happy to include it. Finally, do you think the package maintainers could be persuaded to upload packages (or package definition files) to a stable location? Or do they do this already? We could do that if somebody setups the server. That kind of archive should be possible on archive.buildserver.net. In that case the RPMs would mingle just nicely in between the deb-structure. For now we don't export the urpmi and ap4rpm style lists, but this could be added to the dak if someone stands up to doing this. The ideas are all there. ;) -- Best regards, Kilian signature.asc Description: Digital signature ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-list] Ekiga, siproxd on Debian Etch troubles.
Damien, Bad luck; Check this page http://status.buildserver.net/packages/status.php etch is having a problem building opal Weird, because the failure cause has been fixed by myself last week-end. And it really seems the last try to build happened on the 1st of June. So the build system is stopped. yes, the usual hang in the cvs2cl.. thanks for the hint. should be fixed now. -- Best regards, Kilian signature.asc Description: Digital signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] stun.ekiga.net down
Damien, On Mon, Apr 16, 2007 at 08:08:30PM +0200, Damien Sandras wrote: stun.ekiga.net is down, please use stun.voxgratia.org instead while we are fixing the problem. should be back up. Do you reckon? -- Best regards, Kilian signature.asc Description: Digital signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-devel-list] HELP !!! (Was Re: [VALVE] Ubuntu Edgy)
Tom, Not from you Kilian, Jan, Julien, Yannick. You are already doing a lot for Ekiga. We need fresh air, from new people. Why exclude Kilian? He's a senior and CM for many packages and distros and leading member of distro QA teams and provides valuable You ignore sometimes for reasons that indicate P-CMM issues (not only from the rumors). Any taker ? If Kilian is out, I'm out, too. you misread Damien. He said that he's excluding me from the blame. He's not excluding me from the project. ;) So, no worries, I'm still there and I will be (as will my packs). -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Compiling Problem
Gustavo, On Mon, Jan 15, 2007 at 04:23:25PM -0600, Gustavo Valdes wrote: I'm trying to add some libraries to make the UI skinnable, this libraries belong to a project named SLIK and I'd also want to remove or hide some tabs. for SILK, just copy a target like libxml2 or libogg (3 targets overall). Add the last lib/libsilk.a to the depends of ekiga/config.status. Then go ahead and update the tarball or hack away with the ekiga/ directory. Touch ekiga/autogen.sh will cause make all to refresh all subsequent targets. Hth. -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Compiling Problem
Gustavo, On Mon, Jan 15, 2007 at 03:47:10PM -0600, Gustavo Valdes wrote: What if I need to change or add some features to the program and I need to compile against that new code? basically add it to [the build-depends of] the target you need it compiled (that new code). It's all in the make syntax and dependency chains. If you can bring a more straightforward question what kind of code you need to add and where to I can give you more direct instructions. -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Compiling Problem
Gustavo, On Mon, Dec 18, 2006 at 01:22:17PM -0600, Gustavo Valdes wrote: I plan to distribute it within a company but I'd like to share the code, once made. About compiling on windows ... any clue to get rid of config.h dependency??? I'm checking the windows version you've made an in the account screen the account type combo (to choose from SIP or H323) does not appear as it does in the manual screenshots. what about the scripts that are on the webpage, namely: http://snapshots.ekiga.net/win32/ekiga_build.tgz ? Does that answer your question how we actually get rid of all the problems? -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] problems compiling v4l2
Hi again, whoever has tried searching a fix for this, the Ubuntu packs are building again and the V4L2 detection now works perfect. Thanks goes to Luc Saillard! -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga cross compilation
Dcak, On Thu, Nov 23, 2006 at 11:56:03AM +0530, Dheepan A.P wrote: please help me how to cross compile ekiga(specially pwlib directory) on montovista.At present it is compiled in gcc try reading http://snapshots.ekiga.net/win32.php ... Especially the part at the bottom where it reads these are the scripts we use for cross-compilation. -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] problems compiling v4l2
Hi guys, as some of you may already have noticed, there are no really current Ubuntu snapshots from CVS since some time (for all architectures). For some reason the v4l2 test fails on Ubuntu due to the other headers that are pulled in by autoconf. The result from configure (taken from plugins/config.log on ppc dapper) is as follows: -(snip)- configure:3979: checking for linux/videodev2.h configure:4000: gcc -c -g -O2 conftest.c 5 In file included from conftest.c:25: /usr/include/linux/time.h:9: error: redefinition of 'struct timespec' /usr/include/linux/time.h:15: error: redefinition of 'struct timeval' In file included from /usr/include/linux/videodev2.h:16, from conftest.c:29: /usr/include/sys/time.h:57: error: redefinition of 'struct timezone' /usr/include/sys/time.h:94: error: syntax error before numeric constant /usr/include/sys/time.h:108: error: redefinition of 'struct itimerval' configure:4006: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME | #define PACKAGE_TARNAME | #define PACKAGE_VERSION | #define PACKAGE_STRING | #define PACKAGE_BUGREPORT | #ifdef __cplusplus | extern C void std::exit (int) throw (); using std::exit; | #endif | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | /* end confdefs.h. */ | | #ifdef __linux__ | #include linux/types.h | #include linux/time.h | #endif | | | #include linux/videodev2.h configure:4030: result: no configure:4037: checking for V4L2 video support configure:4045: result: no -(snip)- Someone got any idea how to cleanly fix this and can bring forth a proper patch to apply upstream? -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Patch to remove some code
On Sun, Nov 05, 2006 at 06:47:29PM +0100, Damien Sandras wrote: Le dimanche 05 novembre 2006 à 17:57 +0100, Julien Puydt a écrit : Damien Sandras a écrit : If you are 100% sure it doesn't break anything, yes. This function is only used in gmconf-glib.c, and as far as I know, the win32 port is compiled against glib 2.12 now (and probably a newer version when we'll move to gtk+ 2.10). Well, Windows Millenium only has GTK+ 2.6 available. Well, WinME has no security support anymore. Thus, whoever is running this OS shouldn't be doing it networked. Obviously non-networked workstations are not really best choice for running a VoIP softphone. IMHO, Snark's patch is ok, as at some point we need to move. I haven't checked Sarge and RHEL9 though. As neither of which does build for other reasons (without proper backports) AFAIK, we can plain proceed. Just my 2 €-ct. -- Best regards, Kilian ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Ekiga/win32 links again
Hi guys, ok, after some long trial and error hours of compilation Julien helped me to finally get the compilation scripting up to the current codebase. Right now, we can link Ekiga (untested, plain CompilesForMe(TM)), but it ships no codec plugins whatsoever. Thus, someone(tm) or anyone(tm) needs to take the diff/opal_Makefile.am and check what's still missing to complete the migration towards plugins. Most probably PWLib plugins also need to be added. In short: we're searching for skilled betatesters listing what's missing and what they can identify (most preferably with patches). The latest version of our work is right now temporarily hosted at http://trinity.buildserver.net/~kk/ where you'll find the scripts under ekiga_win32_build and results under dist/. Feel free to test all of this, same rules as are on http://snapshots.ekiga.net/win32.php apply. Once we get past this final step, win32 snapshots will be done live and updated again and next to come would be putting the autotools efforts into CVS to merge all of this upstream of course (after thorough testing of course). -- Best regards, Kilian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Where I get the source??
Wolf, Am Samstag, den 21.10.2006, 05:44 +0200 schrieb Wolf St. Kappesser: call me stupid (i m from windows world ;)) but i couldn t find the source there is only the binary (which run on my system well) on the bottom links. Would be thankfull for some explanating words. I guess the most convenient until the CVS problem is solved is to use the checkout tarball from: http://snapshots.ekiga.net/cvs/ekiga-cvs.tar.gz That one is constantly updated, so it should give you about the same versions as a fresh CVS checkout. Latency may be up to an hour, but you'll manage to sustain that, eh? ;) For the win32 building, that script which was already mentioned is updated already and I'm through till getting ekiga compile at last. If anyone is interested, the updated version is at: http://archive.buildserver.net/win32/ekiga_win32_build_20061023.tbz That one should at least get you pretty well started in case you own a linux shell to run this script set on. -- Best regards, Kilian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
