Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x

2013-01-30 Thread Markus Elfring
 Where did you download opal and ptlib from?

I have got these software libraries from the official repositories.


 What version?

  | Subversion |  openSUSE
--++-
ptlib | 2.12   | 2.10.5-2.1.2
opal  | 3.12   | 3.10.5-2.1.2


See also update candidates for a few corresponding plug-ins:
https://sourceforge.net/tracker/?func=detailatid=989748aid=3600658group_id=204472
https://sourceforge.net/tracker/?func=detailatid=989748aid=3602450group_id=204472
https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472

Regards,
Markus
___
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x

2013-01-30 Thread Eugen Dedu

On 30/01/13 09:44, Markus Elfring wrote:

Where did you download opal and ptlib from?


I have got these software libraries from the official repositories.



What version?


   | Subversion |  openSUSE
--++-
ptlib | 2.12   | 2.10.5-2.1.2
opal  | 3.12   | 3.10.5-2.1.2


The problem is that ekiga is tested with 2.10/3.10 versions, as shown at 
http://wiki.ekiga.org/index.php/Download_Ekiga_sources.  It has not been 
tested with .12 versions, and there are API breakages, as you noticed.


Do you have a strong reason to use .12 versions?  I suggest you to use 
.10 version.



See also update candidates for a few corresponding plug-ins:
https://sourceforge.net/tracker/?func=detailatid=989748aid=3600658group_id=204472
https://sourceforge.net/tracker/?func=detailatid=989748aid=3602450group_id=204472
https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472


Yes, I have seen them, thank you.

--
Eugen
___
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x

2013-01-30 Thread Markus Elfring
 If your kdevelop uses gcc 4.4.1, then this could easily be explained, since
 recent gcc have become stricter and stricter about the C syntax.

No - This integrated development environment calls just the compiler version
(g++ 4.7.1) that is provided by the openSUSE distribution here.


 If you need ekiga as a user, then use v10.

I can refer also to this version level if I pass appropriate values for
parameters like PTLIB_CFLAGS and OPAL_CFLAGS to the command configure. But
I still wonder about results like the following.

...
make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/lib'
  CXX  videoinput-manager-ptlib.lo
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual bool GMVideoInputManager_ptlib::open(unsigned int, unsigned int,
unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:152:17: error:
'class PVideoInputDevice' has no member named 'GetParameters'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_colour(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:201:19: error:
'class PVideoInputDevice' has no member named 'SetColour'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_brightness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:208:19: error:
'class PVideoInputDevice' has no member named 'SetBrightness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_whiteness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:215:19: error:
'class PVideoInputDevice' has no member named 'SetWhiteness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_contrast(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:222:19: error:
'class PVideoInputDevice' has no member named 'SetContrast'
make[3]: *** [videoinput-manager-ptlib.lo] Error 1
  CXX  opal-call-manager.lo
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'virtual
void Opal::CallManager::set_maximum_jitter(unsigned int)':
../lib/engine/components/opal/opal-call-manager.cpp:230:28: error: no matching
function for call to 'max(unsigned int, int)'
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note: candidates 
are:
In file included from /usr/include/c++/4.7/algorithm:62:0,
 from ../lib/engine/components/opal/opal-call-manager.cpp:38:
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note: templateclass _Tp const
_Tp std::max(const _Tp, const _Tp)
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note:   template argument
deduction/substitution failed:
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note:   deduced
conflicting types for parameter 'const _Tp' ('unsigned int' and 'int')
...
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'void
Opal::CallManager::set_video_options(const Opal::CallManager::VideoOptions)':
../lib/engine/components/opal/opal-call-manager.cpp:600:40: error:
'RateControlPeriodOption' is not a member of 'OpalVideoFormat'
In file included from /usr/local/include/ptclib/threadpool.h:44:0,
 from /usr/local/include/ptlib/timer.h:43,
 from /usr/local/include/ptlib.h:66,
 from ../lib/engine/components/opal/opal-call-manager.h:45,
 from ../lib/engine/components/opal/opal-call-manager.cpp:41:
/usr/local/include/ptlib/safecoll.h: In instantiation of 'PSafePtrT,
BaseClass::operator T*() const [with T = OpalMediaPatch; BaseClass =
PSafePtrMultiThreaded]':
/usr/include/opal/opal/mediastrm.h:384:48:   required from here
/usr/local/include/ptlib/safecoll.h:900:80: error: cannot dynamic_cast '((const
PSafePtrOpalMediaPatch, PSafePtrMultiThreaded*)this)-PSafePtrOpalMediaPatch,
PSafePtrMultiThreaded::anonymous.PSafePtrMultiThreaded::anonymous.PSafePtrBase::currentObject'
(of type 'class PSafeObject* const') to type 'class OpalMediaPatch*' (target is
not pointer or reference to complete type)
In file included from /usr/include/opal/opal/mediafmt.h:47:0,
 from /usr/include/opal/opal/mediastrm.h:43,
 from /usr/include/opal/im/im.h:71,
 from /usr/include/opal/opal/pres_ent.h:43,
 from /usr/include/opal/opal/manager.h:41,
 from /usr/include/opal/opal/endpoint.h:41,
 from /usr/include/opal/opal/rtpep.h:38,
 from /usr/include/opal/h323/h323ep.h:45,
 from /usr/include/opal/h323/h323.h:39,
 from ../lib/engine/components/opal/opal-call-manager.h:47,
 from ../lib/engine/components/opal/opal-call-manager.cpp:41:
...


Regards,
Markus

Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x

2013-01-30 Thread Julien Puydt

Le 30/01/2013 22:22, Markus Elfring a écrit :

If your kdevelop uses gcc 4.4.1, then this could easily be explained, since
recent gcc have become stricter and stricter about the C syntax.


No - This integrated development environment calls just the compiler version
(g++ 4.7.1) that is provided by the openSUSE distribution here.



If you need ekiga as a user, then use v10.


I can refer also to this version level if I pass appropriate values for
parameters like PTLIB_CFLAGS and OPAL_CFLAGS to the command configure. But
I still wonder about results like the following.


Why do you wonder? Obviously the code isn't supposed to be compatible 
with v12, and the configure script has a bug in that it doesn't detect 
this problem.


Snark
___
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-devel-list