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

On 30/01/13 17:51, Markus Elfring wrote:
It has not been tested with .12 versions, and there are API breakages, as you noticed.

But I find it strange that a member function like "PVideoDevice::GetParameters"
should not be accessible by the pointer "input_device" (class
"PVideoInputDevice") for example.

I do not see problems by the view from the tool "KDevelop 4-4.4.1-73.1" while
the tool "g++ 4.7.1 20120723" complains about some source code places here.

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.

I interpret the use of the prefix "opal/" in your include statements as another
update candidate.

How do you think about to delete it there and let it be added to the include
parameters by your configuration script instead?

No. For simplicity, ekiga depends strictly on some version of ptlib/opal. When we switch to v12, then we fix/update ekiga code to work with it.

Do you have a strong reason to use .12 versions?

I would like to try out some of the latest stable software libraries your
application depends on.

v12 is not well tested with ekiga and based on my experience I am sure that v12 needs many fixes to be as good as v10.

If you need ekiga as a user, then use v10. If you want to do development work, then you can try v12 and inform us about the patches you use so that we can commit them when we switch to v12 (in very few months).


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]