Re: [Ekiga-devel-list] [Win32] libboost compiling - trouble with opal
Thierry Simonnet schrieb: If somebody is interested, I succeed to compile libbost under linux for win 32 with mingw . 1/ download last version of libboost : boost_1_40_0.tar.gz 2/ uncompress 3/ generate bjam for local platform : sh bootstrap.sh 4/ create a config file for mingw : * touch user-config.jam * echo "using gcc : : i586-mingw32msvc-gcc : ; " > user-config.jam 5/ generate library (don't know which one I will use yet) * .dll : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=shared runtime-link=shared toolset=gcc target-os=windows threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage * .a : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=static runtime-link=static toolset=gcc threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage * .lib : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=static runtime-link=static toolset=gcc target-os=windows threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage 6/ execute i586-mingw32svc-ranlib on library Ptlib/trunk is ok now. Next step opal/trunk : [CC] src/codec/g711a1_plc.cxx [AR] lib_mingw_x86/libopal_s.a i586-mingw32msvc-ranlib /root/win32/opal/lib_mingw_x86/libopal_s.a [LD] lib_mingw_x86/libopal.3.7-beta1.dll /root/win32/opal/lib_mingw_x86/obj/connection.o:connection.cxx:(.text+0x3587): undefined reference to `OpalEchoCanceler::SetParameters(OpalEchoCanceler::Params const&)' /root/win32/opal/lib_mingw_x86/obj/connection.o:connection.cxx:(.text+0x35a3): undefined reference to `OpalEchoCanceler::SetClockRate(int)' /root/win32/opal/lib_mingw_x86/obj/pcss.o:pcss.cxx:(.text+0xcf0): undefined reference to `OpalEchoCanceler::OpalEchoCanceler()' /root/win32/opal/lib_mingw_x86/obj/pcss.o:pcss.cxx:(.text+0xe84): undefined reference to `OpalEchoCanceler::OpalEchoCanceler()' collect2: ld returned 1 exit status make[1]: *** [/root/win32/opal/lib_mingw_x86/libopal.3.7-beta1.dll] Error 1 make[1]: Leaving directory `/root/win32/opal' make: *** [/root/win32/lib/libopal_s.a] Error 2 Great work on boost, I will try your approach tomorrow. As to the Opal error, give attached patch a try. It helped me. Michael diff -ur opal.orig/Makefile.in opal/Makefile.in --- opal.orig/Makefile.in 2009-09-30 16:08:59.0 +0200 +++ opal/Makefile.in 2009-09-30 16:10:44.0 +0200 @@ -391,6 +391,7 @@ $(OPAL_SRCDIR)/codec/rfc2833.cxx \ $(OPAL_SRCDIR)/codec/opalwavfile.cxx \ $(OPAL_SRCDIR)/codec/silencedetect.cxx \ + $(OPAL_SRCDIR)/codec/echocancel.cxx \ $(OPAL_SRCDIR)/codec/opalpluginmgr.cxx \ $(OPAL_SRCDIR)/codec/ratectl.cxx @@ -415,8 +416,7 @@ VPATH_C += $(SPEEXDSP_SRCDIR) VPATH_CXX += $(SPEEXDSP_SRCDIR) -SOURCES += $(OPAL_SRCDIR)/codec/echocancel.cxx \ - $(SPEEXDSP_SRCDIR)/speex_preprocess.c \ +SOURCES += $(SPEEXDSP_SRCDIR)/speex_preprocess.c \ $(SPEEXDSP_SRCDIR)/smallft.c \ $(SPEEXDSP_SRCDIR)/misc.c \ $(SPEEXDSP_SRCDIR)/mdf.c \ ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] [Win32] libboost compiling - trouble with opal
If somebody is interested, I succeed to compile libbost under linux for win 32 with mingw . 1/ download last version of libboost : boost_1_40_0.tar.gz 2/ uncompress 3/ generate bjam for local platform : sh bootstrap.sh 4/ create a config file for mingw : * touch user-config.jam * echo "using gcc : : i586-mingw32msvc-gcc : ; " > user-config.jam 5/ generate library (don't know which one I will use yet) * .dll : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=shared runtime-link=shared toolset=gcc target-os=windows threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage * .a : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=static runtime-link=static toolset=gcc threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage * .lib : ./bjam --user-config=user-config.jam --layout=system variant=release threading=multi link=static runtime-link=static toolset=gcc target-os=windows threadapi=win32 --without-math --without-python --without-mpi --without-serialization --without-test --without-thread --without-wave --without-date_time --without-system --without-filesystem --without-graph --without-iostreams --without-program_options --without-regex stage 6/ execute i586-mingw32svc-ranlib on library Ptlib/trunk is ok now. Next step opal/trunk : [CC] src/codec/g711a1_plc.cxx [AR] lib_mingw_x86/libopal_s.a i586-mingw32msvc-ranlib /root/win32/opal/lib_mingw_x86/libopal_s.a [LD] lib_mingw_x86/libopal.3.7-beta1.dll /root/win32/opal/lib_mingw_x86/obj/connection.o:connection.cxx:(.text+0x3587): undefined reference to `OpalEchoCanceler::SetParameters(OpalEchoCanceler::Params const&)' /root/win32/opal/lib_mingw_x86/obj/connection.o:connection.cxx:(.text+0x35a3): undefined reference to `OpalEchoCanceler::SetClockRate(int)' /root/win32/opal/lib_mingw_x86/obj/pcss.o:pcss.cxx:(.text+0xcf0): undefined reference to `OpalEchoCanceler::OpalEchoCanceler()' /root/win32/opal/lib_mingw_x86/obj/pcss.o:pcss.cxx:(.text+0xe84): undefined reference to `OpalEchoCanceler::OpalEchoCanceler()' collect2: ld returned 1 exit status make[1]: *** [/root/win32/opal/lib_mingw_x86/libopal.3.7-beta1.dll] Error 1 make[1]: Leaving directory `/root/win32/opal' make: *** [/root/win32/lib/libopal_s.a] Error 2 -- Thierry Simonnet ESIEE-Paris Par respect pour l’environnement, n’imprimez ce mail que si nécessaire ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
Michael Cronenworth wrote: > How about performance profiling? Ekiga may not be responsible, but on a > good video phone call I will see at least one core at 100% CPU usage on > a brand new Core 2 Duo system. Would it be good to profile the OPAL > and/or ptlib as well as Ekiga to get CPU usage down? I consider this to be important, too. See Launchpad bug #395594 'Ekiga occupies > 82% of a Centrino computer's CPU time' Regards, Detlef Lechner ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
On Wed, Sep 30, 2009 at 9:51 AM, yannick wrote: > Eugen Dedu a écrit : >> Michael Cronenworth wrote: >>> On 09/27/2009 05:19 AM, Damien Sandras wrote: Comments ? >>> How about performance profiling? Ekiga may not be responsible, but on a >>> good video phone call I will see at least one core at 100% CPU usage on >>> a brand new Core 2 Duo system. Would it be good to profile the OPAL >>> and/or ptlib as well as Ekiga to get CPU usage down? Skype, even though >>> it's pretty much junk, uses less CPU. >>> >>> This CPU power draw reduces battery life on laptops, causes higher heat >>> output, etc. >> >> This is a good point too, there is already >> https://bugzilla.gnome.org/show_bug.cgi?id=581019, we just need someone >> to do it :o) >> > and this one: > https://bugzilla.gnome.org/show_bug.cgi?id=591627 I have a similarly related bug on the Fedora bugzilla about the amount of bandwidth that ekiga uses when idle. https://bugzilla.redhat.com/show_bug.cgi?id=490605 I've not had a chance to actually look at it any further and I don't know enough about the SIP spec to know how often it needs to communicate with the server to notify its still alive. Peter ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
Eugen Dedu a écrit : > Michael Cronenworth wrote: >> On 09/27/2009 05:19 AM, Damien Sandras wrote: >>> Comments ? >>> >> How about performance profiling? Ekiga may not be responsible, but on a >> good video phone call I will see at least one core at 100% CPU usage on >> a brand new Core 2 Duo system. Would it be good to profile the OPAL >> and/or ptlib as well as Ekiga to get CPU usage down? Skype, even though >> it's pretty much junk, uses less CPU. >> >> This CPU power draw reduces battery life on laptops, causes higher heat >> output, etc. > > This is a good point too, there is already > https://bugzilla.gnome.org/show_bug.cgi?id=581019, we just need someone > to do it :o) > and this one: https://bugzilla.gnome.org/show_bug.cgi?id=591627 ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
Michael Cronenworth wrote: > On 09/27/2009 05:19 AM, Damien Sandras wrote: >> Comments ? >> > > How about performance profiling? Ekiga may not be responsible, but on a > good video phone call I will see at least one core at 100% CPU usage on > a brand new Core 2 Duo system. Would it be good to profile the OPAL > and/or ptlib as well as Ekiga to get CPU usage down? Skype, even though > it's pretty much junk, uses less CPU. > > This CPU power draw reduces battery life on laptops, causes higher heat > output, etc. This is a good point too, there is already https://bugzilla.gnome.org/show_bug.cgi?id=581019, we just need someone to do it :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] Opal 3.6.6 build problem
László Monda a écrit : > On Wed, Sep 30, 2009 at 8:17 AM, Damien Sandras wrote: >> Le mardi 29 septembre 2009 à 19:26 +0200, yannick a écrit : >>> László Monda a écrit : I'm disappointed about the current situation. How about creating an APT repository for Ekiga and its dependencies for the recent Ubuntu releases? >>> Done: >>> https://launchpad.net/~sevmek/+archive/ekiga-released >>> (for Jaunty and Karmic) >>> I'm working for 8.04 Hardy, but it is tricky... >>> Would it override the official Ubuntu packages? >>> You need to add it manually, after that it will overwrite (see the >>> description) >>> It could be even put to the Ekiga site. >>> That's the plan, but I've some work to do on ekiga.org first... Should >>> be ready in a few weeks. >> It should become our first priority. After all, it is our "vitrin". > > I would help on this by authoring the site if it would be MediaWiki > based, but custom sites are often make authoring too much of a pain. > We will go drupal http://drupal.org/ Damien is right, hopefully I'll find some time to start the theme today. ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
