Re: [Ekiga-devel-list] Unable to compile
Shiva wrote: Hi team, I'm a new member of this group. I need one SIP client, so i selected 'Ekiga'. I tried to compile the source by './configure', I'm facing an error. The error is mentioned below: checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 1572864 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag F77 to libtool checking for gcc option to accept ISO C99... unsupported checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached)
Re: [Ekiga-devel-list] Need clarification
Sumathi wrote: Hi All, I have downloaded Ekiga source to work with Ekiga.. I am using Eclipse IDE to work with the Ekiga. While i am building an Ekiga source, i am getting following error message. the error message are attached.. Well, config.h is in /home/parasuraman/Workspace_cpp/Egika and somehow you should include it in -I flags. I don't know how eclipse work, why it has not included it... -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] ekiga description
Hi, I am writing the doap file. The shortdesc should be changed, because it speaks only about talk, not video. Now it is shortdesc xml:lang=enTalk to people over the Internet/shortdesc and i want to change it to shortdesc xml:lang=enTalk to people and see them over the Internet/shortdesc Do you have better ideas? (This will also change the ekiga.desktop file.) -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga description
Might be better to have Talk to and see people over the internet Peter On Mon, Apr 20, 2009 at 5:14 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: Hi, I am writing the doap file. The shortdesc should be changed, because it speaks only about talk, not video. Now it is shortdesc xml:lang=enTalk to people over the Internet/shortdesc and i want to change it to shortdesc xml:lang=enTalk to people and see them over the Internet/shortdesc Do you have better ideas? (This will also change the ekiga.desktop file.) -- Eugen ___ 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] ekiga.rc
Michael Rickmann wrote: Am Sonntag, den 19.04.2009, 18:53 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Samstag, den 18.04.2009, 14:57 +0200 schrieb Julien Puydt: Eugen Dedu a écrit : Is there a way to move ekiga.rc from root to win32? 1) git mv ekiga.rc win32/ 2) make sure any file referencing ekiga.rc now searches for it in win32/ Snark Could you please rename it so that the basename is distinctive, e.g. ekiga-rc.rc ? I ask this because eventually we can include compilation of the resources into the autoconf/libtool make process and then an ekiga.o file would be a bit dangerous I think. Additionally VALUE SpecialBuild, CVS_VERSION in the resource file is a bit outdated. Now an EKIGA_REVISION is defined in src/revision.h . See attached patch as an example for how one could handle the Win32 resources. Note that ekiga uses git now, so src/Makefile.am info about revision.h is obsolete... Is it interesting to resuscitate it? -- Eugen Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. For my snapshots, I use only the date in the .deb file name (see http://snapshots.ekiga.net/snapshots/debian/). Users can know the version (the date) with 'dpkg -l' afterwards. Wouldn't this be sufficient for windows snapshots too? (Simpler is better :o)) -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga description
Hrmm how about Video conference with people over the internet as when I hear the term video conference it automatically implies the talking piece of it. -C On Mon, Apr 20, 2009 at 12:16 PM, Peter Robinson pbrobin...@gmail.comwrote: Might be better to have Talk to and see people over the internet Peter On Mon, Apr 20, 2009 at 5:14 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: Hi, I am writing the doap file. The shortdesc should be changed, because it speaks only about talk, not video. Now it is shortdesc xml:lang=enTalk to people over the Internet/shortdesc and i want to change it to shortdesc xml:lang=enTalk to people and see them over the Internet/shortdesc Do you have better ideas? (This will also change the ekiga.desktop file.) -- Eugen ___ 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 ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga.rc
Is there a way to move ekiga.rc from root to win32? 1) git mv ekiga.rc win32/ 2) make sure any file referencing ekiga.rc now searches for it in win32/ Snark Could you please rename it so that the basename is distinctive, e.g. ekiga-rc.rc ? I ask this because eventually we can include compilation of the resources into the autoconf/libtool make process and then an ekiga.o file would be a bit dangerous I think. Additionally VALUE SpecialBuild, CVS_VERSION in the resource file is a bit outdated. Now an EKIGA_REVISION is defined in src/revision.h . See attached patch as an example for how one could handle the Win32 resources. Note that ekiga uses git now, so src/Makefile.am info about revision.h is obsolete... Is it interesting to resuscitate it? -- Eugen Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. For my snapshots, I use only the date in the .deb file name (see http://snapshots.ekiga.net/snapshots/debian/). Users can know the version (the date) with 'dpkg -l' afterwards. Wouldn't this be sufficient for windows snapshots too? (Simpler is better :o)) I would personally prefer the git version rather than the date version as there could be multiple different versions of ekiga on a single day dependant on the amount of commits. By using the git rev you know exactly what the build was based upon so it makes it easier from a debug and recreation of the problem perpective. Regards, Peter ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga.rc
Am Montag, den 20.04.2009, 18:12 +0100 schrieb Peter Robinson: Is there a way to move ekiga.rc from root to win32? 1) git mv ekiga.rc win32/ 2) make sure any file referencing ekiga.rc now searches for it in win32/ Snark Could you please rename it so that the basename is distinctive, e.g. ekiga-rc.rc ? I ask this because eventually we can include compilation of the resources into the autoconf/libtool make process and then an ekiga.o file would be a bit dangerous I think. Additionally VALUE SpecialBuild, CVS_VERSION in the resource file is a bit outdated. Now an EKIGA_REVISION is defined in src/revision.h . See attached patch as an example for how one could handle the Win32 resources. Note that ekiga uses git now, so src/Makefile.am info about revision.h is obsolete... Is it interesting to resuscitate it? -- Eugen Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. For my snapshots, I use only the date in the .deb file name (see http://snapshots.ekiga.net/snapshots/debian/). Users can know the version (the date) with 'dpkg -l' afterwards. Wouldn't this be sufficient for windows snapshots too? (Simpler is better :o)) I would personally prefer the git version rather than the date version as there could be multiple different versions of ekiga on a single day dependant on the amount of commits. By using the git rev you know exactly what the build was based upon so it makes it easier from a debug and recreation of the problem perpective. Regards, Peter I agree, currently it is used for ptracing for linux and windows, gui/main.cpp: PTRACE(1, Ekiga SVN revision: EKIGA_REVISION); To have it in the Windows resources too, is for right clicking on ekiga.exe and have people find the revision under properties. Regards Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga.rc
Peter Robinson wrote: Is there a way to move ekiga.rc from root to win32? 1) git mv ekiga.rc win32/ 2) make sure any file referencing ekiga.rc now searches for it in win32/ Snark Could you please rename it so that the basename is distinctive, e.g. ekiga-rc.rc ? I ask this because eventually we can include compilation of the resources into the autoconf/libtool make process and then an ekiga.o file would be a bit dangerous I think. Additionally VALUE SpecialBuild, CVS_VERSION in the resource file is a bit outdated. Now an EKIGA_REVISION is defined in src/revision.h . See attached patch as an example for how one could handle the Win32 resources. Note that ekiga uses git now, so src/Makefile.am info about revision.h is obsolete... Is it interesting to resuscitate it? -- Eugen Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. For my snapshots, I use only the date in the .deb file name (see http://snapshots.ekiga.net/snapshots/debian/). Users can know the version (the date) with 'dpkg -l' afterwards. Wouldn't this be sufficient for windows snapshots too? (Simpler is better :o)) I would personally prefer the git version rather than the date version as there could be multiple different versions of ekiga on a single day dependant on the amount of commits. By using the git rev you know exactly what the build was based upon so it makes it easier from a debug and recreation of the problem perpective. The snapshots will be done weekly, isn't the day sufficient? For debian the day was not sufficient only once in one year (since they exist). And if unsure, the next snapshot can be used. -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] pwlib.pc in windows
Am Montag, den 20.04.2009, 19:38 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Montag, den 20.04.2009, 18:49 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Sonntag, den 19.04.2009, 15:01 +0200 schrieb Eugen Dedu: Hi, Is win32/diff/ptlib_pwlib.pc.in still used? None of the diffs in the win32 subdir is used any longer. Could win32/diff directory be removed completely? Yes, I think that Win32 Ekiga will be built without separate configuration files and patches. None of the files in the current diff dir is used for current builds. May be that we will need a patch to make the directx headers temporarily compatible with the configure of ptlib. But I think I can fix that directly. Michael The goal is to have all windows (debian etc.) patches integrated upstream. If needed, a patch could be put temporarily in win32. So I wanted to remove completely win32/diff, but I had just noticed that the diff directory is used in the win32/Makefile (search for diff, afterwards DIFF). Are you sure win32/diff can be removed?? It can be removed, perhaps not now. That will break the Makefile even more - there are lots of dependencies on the unused configuration files. Currently, the Makefile is broken and outdated anyhow. My suggestion is that we wait until Win32 Ekiga 3.2 is usable including VFW, DirectX, provide a new Makefile and remove the diff dir then. Regards Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] pwlib.pc in windows
Michael Rickmann wrote: Am Montag, den 20.04.2009, 19:38 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Montag, den 20.04.2009, 18:49 +0200 schrieb Eugen Dedu: Michael Rickmann wrote: Am Sonntag, den 19.04.2009, 15:01 +0200 schrieb Eugen Dedu: Hi, Is win32/diff/ptlib_pwlib.pc.in still used? None of the diffs in the win32 subdir is used any longer. Could win32/diff directory be removed completely? Yes, I think that Win32 Ekiga will be built without separate configuration files and patches. None of the files in the current diff dir is used for current builds. May be that we will need a patch to make the directx headers temporarily compatible with the configure of ptlib. But I think I can fix that directly. Michael The goal is to have all windows (debian etc.) patches integrated upstream. If needed, a patch could be put temporarily in win32. So I wanted to remove completely win32/diff, but I had just noticed that the diff directory is used in the win32/Makefile (search for diff, afterwards DIFF). Are you sure win32/diff can be removed?? It can be removed, perhaps not now. That will break the Makefile even more - there are lots of dependencies on the unused configuration files. Currently, the Makefile is broken and outdated anyhow. My suggestion is that we wait until Win32 Ekiga 3.2 is usable including VFW, DirectX, provide a new Makefile and remove the diff dir then. Very well! -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga.rc
Michael Rickmann wrote: Am Montag, den 20.04.2009, 18:12 +0100 schrieb Peter Robinson: Is there a way to move ekiga.rc from root to win32? 1) git mv ekiga.rc win32/ 2) make sure any file referencing ekiga.rc now searches for it in win32/ Snark Could you please rename it so that the basename is distinctive, e.g. ekiga-rc.rc ? I ask this because eventually we can include compilation of the resources into the autoconf/libtool make process and then an ekiga.o file would be a bit dangerous I think. Additionally VALUE SpecialBuild, CVS_VERSION in the resource file is a bit outdated. Now an EKIGA_REVISION is defined in src/revision.h . See attached patch as an example for how one could handle the Win32 resources. Note that ekiga uses git now, so src/Makefile.am info about revision.h is obsolete... Is it interesting to resuscitate it? -- Eugen Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. It's ok for me. How did you obtain 80 and g80bf...? I couldn't find them on http://git.gnome.org/cgit/ekiga/, neither with git log on both trunk and gnome-2-26. I didn't know it is possible to number the revisions (80) in git. For my snapshots, I use only the date in the .deb file name (see http://snapshots.ekiga.net/snapshots/debian/). Users can know the version (the date) with 'dpkg -l' afterwards. Wouldn't this be sufficient for windows snapshots too? (Simpler is better :o)) I would personally prefer the git version rather than the date version as there could be multiple different versions of ekiga on a single day dependant on the amount of commits. By using the git rev you know exactly what the build was based upon so it makes it easier from a debug and recreation of the problem perpective. Regards, Peter I agree, currently it is used for ptracing for linux and windows, gui/main.cpp: PTRACE(1, Ekiga SVN revision: EKIGA_REVISION); To have it in the Windows resources too, is for right clicking on ekiga.exe and have people find the revision under properties. Ok. -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga description
Ok, that covers the video part then.. Converse with family, friends and business associates over the internet? -C On Mon, Apr 20, 2009 at 1:17 PM, Peter Robinson pbrobin...@gmail.comwrote: Looking at what I currently have in Fedora when I hover over the icon I get two lines. The first is IP Telephany, VoIP and Video Conferencing And the following line is Talk to people over the internet So I think its a second line, with the first one already mentioning video conferencing. Peter On Mon, Apr 20, 2009 at 6:08 PM, Christopher Warner cwar...@kernelcode.com wrote: Hrmm how about Video conference with people over the internet as when I hear the term video conference it automatically implies the talking piece of it. -C On Mon, Apr 20, 2009 at 12:16 PM, Peter Robinson pbrobin...@gmail.com wrote: Might be better to have Talk to and see people over the internet Peter On Mon, Apr 20, 2009 at 5:14 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: Hi, I am writing the doap file. The shortdesc should be changed, because it speaks only about talk, not video. Now it is shortdesc xml:lang=enTalk to people over the Internet/shortdesc and i want to change it to shortdesc xml:lang=enTalk to people and see them over the Internet/shortdesc Do you have better ideas? (This will also change the ekiga.desktop file.) -- Eugen ___ 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 ___ 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 ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] another two Win32 crashes
Am Mittwoch, den 15.04.2009, 15:50 +0200 schrieb Eugen Dedu: Damien Sandras wrote: Le mercredi 15 avril 2009 à 09:49 +0200, Michael Rickmann a écrit : 2) When I try to connect to 5...@ekiga.net with echo cancellation enabled I get a crash. Ekiga shows Connected with 5...@ekiga.net Call Duration ... PCMA - H261 and I can hear the female voice before a debugger is attached. You can find the logs at http://wwwuser.gwdg.de/~mrickma/ekiga/logs-win32-crashes.tar.gz They are a bit to long for this mail. Surprisingly the echo cancel crash is triggered from speex/libspeex/kiss_fft.c regardless wether I have enabled the speex codec or not. That's because we are using SPEEX to cancel echo, even if you are not using the speex audio codec, we are still using the internal routines. However, that code has been giving crashes here and there. I'm not sure we can do anything else than disabling it. 1. I see in win32/Makefile:97 that speex is downloaded from Web and that it is version 1.1.12 which is downloaded. Couldn't we take 1.2rc1 from the same URL? 2. I think there is an error in win32/Makefile:381: rm -f $(LIBDIR)/_ibspeex.a should be libspeex instead of _ibspeex, isn't it? -- Eugen To make it short, the crash has disappeared and I do not know why. I could not find any changes in Ekiga's or Opal's GIT/SVN which would directly address this issue. In the meantime I upraded the Mingw runtime and switched to speex 1.2rc1 as Eugene suggested. My ekiga.exe depends on the speex dlls but Opal contains its own speex code which is also used. I think I will investigate later. Regards Michael ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] ekiga description
Its also a short description that needs to be easily translated. Peter On Mon, Apr 20, 2009 at 7:44 PM, Christopher Warner cwar...@kernelcode.com wrote: Ok, that covers the video part then.. Converse with family, friends and business associates over the internet? -C On Mon, Apr 20, 2009 at 1:17 PM, Peter Robinson pbrobin...@gmail.com wrote: Looking at what I currently have in Fedora when I hover over the icon I get two lines. The first is IP Telephany, VoIP and Video Conferencing And the following line is Talk to people over the internet So I think its a second line, with the first one already mentioning video conferencing. Peter On Mon, Apr 20, 2009 at 6:08 PM, Christopher Warner cwar...@kernelcode.com wrote: Hrmm how about Video conference with people over the internet as when I hear the term video conference it automatically implies the talking piece of it. -C On Mon, Apr 20, 2009 at 12:16 PM, Peter Robinson pbrobin...@gmail.com wrote: Might be better to have Talk to and see people over the internet Peter On Mon, Apr 20, 2009 at 5:14 PM, Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote: Hi, I am writing the doap file. The shortdesc should be changed, because it speaks only about talk, not video. Now it is shortdesc xml:lang=enTalk to people over the Internet/shortdesc and i want to change it to shortdesc xml:lang=enTalk to people and see them over the Internet/shortdesc Do you have better ideas? (This will also change the ekiga.desktop file.) -- Eugen ___ 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 ___ 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 ___ 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] ekiga.rc
On Mon, Apr 20, 2009 at 9:17 PM, Michael Cronenworth m...@cchtml.com wrote: Original Message Subject: Re: [Ekiga-devel-list] ekiga.rc From: Michael Rickmann mric...@gwdg.de To: Ekiga development mailing list ekiga-devel-list@gnome.org Date: 04/20/2009 11:54 AM Yes, I have seen that. I am still testing. Would something like #define EKIGA_REVISION EKIGA_3_2_0-80-g80bf6d3 be acceptable in revisioin.h? It is based on the output of git describe, the 80th revision of tag EKIGA_3_2_0 I guess. You cannot do this. Git does not use revision numbers. It uses a commit *hash* for tracking. Don't rely on Git hashes. Define another version number and use that. Its not (at least in fedora) used as a version number, but rather as a tracking bit in builds that aren't final releases to allow tracking of the exact revision. Peter ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Need clarification
Eugen Dedu wrote: Sumathi wrote: Hi All, I have downloaded Ekiga source to work with Ekiga.. I am using Eclipse IDE to work with the Ekiga. While i am building an Ekiga source, i am getting following error message. the error message are attached.. Well, config.h is in /home/parasuraman/Workspace_cpp/Egika and somehow you should include it in -I flags. I don't know how eclipse work, why it has not included it... Hi, I have added -i option in the properties of the Eclipse IDE. Here is the -i options value used.. -I/home/parasuraman/Workspace_cpp/Egika/lib/toolbox -I/home/parasuraman/Workspace_cpp/Egika/src -I/home/parasuraman/Workspace_cpp/Egika/src/gui -I/home/parasuraman/Workspace_cpp/Egika/lib/platform -I/home/parasuraman/Workspace_cpp/Egika/lib/pixops -I/home/parasuraman/Workspace_cpp/Egika/lib/gui -I/home/parasuraman/Workspace_cpp/Egika/lib/gmconf -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/account/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/addressbook/call-history -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/addressbook/evolution -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/addressbook/ldap -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/addressbook/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audioinput/ptlib -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audioinput/null -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audioinput/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audiooutput/null -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audiooutput/ptlib -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/audiooutput/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/chat/echo -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/chat/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/components/avahi-publisher -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/components/gmconf-personal-details -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/framework -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/gui/gtk-core -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/gui/gtk-frontend -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/hal/dbus -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/hal/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/presence/avahi -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/presence/local-roster -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/presence/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/protocol/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videoinput/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videoinput/ptlib -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videoinput/mlogo -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videooutput/x -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videooutput/skel -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videooutput/dx -I/home/parasuraman/Workspace_cpp/Egika/lib/engine/videooutput/common -O0 -g3 -Wall -c -fmessage-length=0 Regards Sumathi ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
