Nabble - kopete-devel

Re: Writing minimal plugin

2009-11-26T13:57:09Z

On Fri, Nov 27, 2009 at 3:12 AM, shiplu <shiplu.net@gmail.com> wrote:

> You need to write it in Qt. To write a plugin for kopete, you need a class
> that derives from Kopete::Plugin. In order to understand how to write a
> plugin I suggest you take a look at code of some existing plugins of kopete.
> There are many. Simplest code I can think of is the code of contactnotes
> plugin. Also take a look at others to understand better.

Where can I find the sources of this plugins?

Please read through http://techbase.kde.org

what is the devel package of kopete in ubuntu? libkopete-dev or
kopete-dev. there is no package like this.

--
A K M Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

--
Greetings,
KDE Developer
irc nick - roide
roideuniverse.blogspot.com

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: Writing minimal plugin

2009-11-26T13:42:08Z

> You need to write it in Qt. To write a plugin for kopete, you need a class
> that derives from Kopete::Plugin. In order to understand how to write a
> plugin I suggest you take a look at code of some existing plugins of kopete.
> There are many. Simplest code I can think of is the code of contactnotes
> plugin. Also take a look at others to understand better.

Where can I find the sources of this plugins?
what is the devel package of kopete in ubuntu? libkopete-dev or
kopete-dev. there is no package like this.

--
A K M Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-26T13:23:25Z

On Thu, 26 Nov 2009 13:53:39 -0200
Gustavo Boiko <gustavo.boiko@...> wrote:

> Well, my test was to remove and not doing a fresh install. If there is just one single libmsn installed, it will show a different error (telling no libmsn.so was found).
>
> If you can do the test I asked for, I would be really glad. I really doubt it is a gcc bug, since it is a damn simple testcase involving pure preprocessing macros (if this is not working in gcc, I know at least 10 other opensource projects that would not be working at all).

Ok Boiko, now I understood what you mean. So:

1) This is the only location I have libmsn installed:

fraga@tux /usr/local/lib$ sudo rm -f libmsn.so*
Password:
fraga@tux /usr/local/lib$ ls libmsn*
ls: cannot access libmsn*: No such file or directory

2) make

fraga@tux ~/svn/kdenetwork/b/kopete/protocols/wlm$ make
[ 0%] Built target kopete_wlm_automoc
[ 0%] Built target kopete_videodevice_automoc
[ 0%] Built target kopete_automoc
[ 8%] Built target kopete_videodevice
[ 83%] Built target kopete
make[2]: *** No rule to make target `/usr/local/lib/libmsn.so', needed by `lib/kopete_wlm.so'. Stop.
make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
make: *** [all] Error 2

***

Now you can be sure there's not any other libmsn installed (I
have a strict control of my computer, so I know where everything is installed). It would be impossible
to have 2 versions, unless it got a major change in the version and even in that case, it normaly would use
the latest version.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-26T11:00:15Z

Hi

On 23/11/2009, at 18:10, Pau Garcia i Quiles wrote:

> On Mon, Nov 23, 2009 at 8:27 PM, Lamarque Vieira Souza
> <lamarque@...> wrote:
>> Em Segunda-feira 23 Novembro 2009, Dâniel Fraga escreveu:
>>> On Mon, 23 Nov 2009 16:10:51 -0200
>>>
>>> Lamarque Vieira Souza <lamarque@...> wrote:
>>>> LIBMSN_INBOX_URL_ENABLED is enabled or g++ would not even try to compile
>>>> line 581. LIBMSN_INBOX_URL_ENABLED is defined in
>>>> /usr/include/msn/config.h (one of
>>>
>>> Ok, but I just said that I never used that option. I mean, if
>>> it's default, I was not aware of it.
>>
>> Thiago added that option to libmsn to make sure no one would break binary
>> compatibility with old libmsn by accident. That option is supposed to be off
>> by default unless Thiago has changed that in newer libmsn versions.
>
> It's ON by default in libmsn 4.0.
>
> Actually, Tiago accidentally broken binary compatibility in beta7 by
> adding a few data members, regardless of what you do with
> LIBMSN_INBOX_URL_ENABLED.

Oups, I will tell Tiago to double check that.

Thanks for pointing.

Cheers

Boiko

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: Writing minimal plugin

2009-11-26T10:51:21Z

Thanks Kaushik for answering my queries.

See my answers in line.

> You need to write it in Qt. To write a plugin for kopete, you need a class
> that derives from Kopete::Plugin. In order to understand how to write a
> plugin I suggest you take a look at code of some existing plugins of kopete.
> There are many. Simplest code I can think of is the code of contactnotes
> plugin. Also take a look at others to understand better. You will see that
> you need to derive a class from kopete::plugin and then it depends on what
> kind of plugin you would like to have.

Okay. My plugin will fetch data from somewhere. It can be web or local media.
When It gets the data, It'll use it to change the current status.
Thats its. So simple.
If such plugin is already available, I wont use that. I want to write
it myself.
This way I'll learn how to write it.

>>
>> Is it possible to use perl/python for plugin?
>> Where can I find the manual?
>
> I am not sure about perl or python. Lets wait for somebody else to answer
> for that.
> And i dont think there is as such manual. If you have problems you can
> always mail us.

Thanks Again.

> --
> Greetings,
> KDE Developer
> irc nick - roide
> roideuniverse.blogspot.com
>
> _______________________________________________
> kopete-devel mailing list
> kopete-devel@...
> https://mail.kde.org/mailman/listinfo/kopete-devel
>
>

--
A K M Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: Writing minimal plugin

2009-11-26T10:43:44Z

I want to write a plugin. I lookup everywhere. Didn't find any clue.

What kind of plugin would you like to write for kopete?

So still I dont know how to write it.
Do I have to write it in C or C++?

You need to write it in Qt. To write a plugin for kopete, you need a class that derives from Kopete::Plugin. In order to understand how to write a plugin I suggest you take a look at code of some existing plugins of kopete. There are many. Simplest code I can think of is the code of contactnotes plugin. Also take a look at others to understand better. You will see that you need to derive a class from kopete::plugin and then it depends on what kind of plugin you would like to have.

Is it possible to use perl/python for plugin?
Where can I find the manual?

I am not sure about perl or python. Lets wait for somebody else to answer for that.

And i dont think there is as such manual. If you have problems you can always mail us.

Writing minimal plugin

2009-11-26T09:59:30Z

Hello,

I want to write a plugin. I lookup everywhere. Didn't find any clue.
So still I dont know how to write it.
Do I have to write it in C or C++?
Is it possible to use perl/python for plugin?
Where can I find the manual?

May be I am missing something very basic.

Any help?

--
A K M Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-26T07:53:39Z

Hi

On 26/11/2009, at 00:54, Dâniel Fraga wrote:

> On Wed, 25 Nov 2009 11:56:45 -0200
> Gustavo Boiko <gustavo.boiko@...> wrote:
>
>> Very unlikely it is.
>>
>> Dâniel, could you please rm -f /usr/local/lib/libmsn.so* and try building wlm again?
>> I'm suspecting it is linking to another libmsn somewhere else.
>
> I already did that. You can bet there is no other libmsn.so
> installed here. I completely removed the old one and installed a fresh
> one.

Well, my test was to remove and not doing a fresh install. If there is just one single libmsn installed, it will show a different error (telling no libmsn.so was found).

> I suggest we create a small c++ code with a ifdef to test if in
> all cases the ifdef is causing this or not.... we could create a small
> sample .cpp file with a .h and I would try to compile it here. If it
> generates some error, I will report to gcc developers... it's the only
> way I think...

If you can do the test I asked for, I would be really glad. I really doubt it is a gcc bug, since it is a damn simple testcase involving pure preprocessing macros (if this is not working in gcc, I know at least 10 other opensource projects that would not be working at all).

Cheers

Boiko
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-26T07:50:59Z

On 26/11/2009, at 00:54, Aleix Pol wrote:

You can easily check that using ldd.
It's useful to check the compilation line using "make VERBOSE=1"

Well, not really true, depending on what -L<dir> flags you are using, the library being used to link the plugin might be different from the one ldd knows about.

Cheers

Boiko

On Wed, Nov 25, 2009 at 2:56 PM, Gustavo Boiko <gustavo.boiko@...> wrote:

On 24/11/2009, at 21:02, Lamarque Vieira Souza wrote:

> Em Terça-feira 24 Novembro 2009, Dâniel Fraga escreveu:
>> On Tue, 24 Nov 2009 16:38:11 -0200
>>
>> Lamarque Vieira Souza <lamarque@...> wrote:
>>> This is weird, if the #ifdef is resolving to false the error message
>>> should be different (like ‘inboxUrl’ was not declared in this scope). You
>>> can confirm if the #ifdef is resolving to true by adding this line inside
>>> the #ifdef:
>>
>> No. The #ifdef is resolving to true, but the reference
>>
>> remains undefined... See below:
>
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6:
>> warning: #warning Inside ifdef
>> (...)
>>
>> Everything is ok until:
>>
>> Linking CXX shared module ../../../lib/kopete_wlm.so
>> CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
>> `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
>> MSN::hotmailInfo)':
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
>> undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)' collect2:
>> ld returned 1 exit status
>> make[2]: *** [lib/kopete_wlm.so] Error 1
>> make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
>> make: *** [all] Error 2
>>
>> Really weird problem...
>
> I agree, it seems more and more like a bug in cpp or g++. One more test, try
> surrounding the newEmailNotification signal with the same #ifdef in
> wlmlibmsn.h to see if starts to have the same problem.

Very unlikely it is.

Dâniel, could you please rm -f /usr/local/lib/libmsn.so* and try building wlm again?
I'm suspecting it is linking to another libmsn somewhere else.

Cheers

Boiko

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-26T05:21:28Z

On Thu, 26 Nov 2009 03:54:27 +0100
Aleix Pol <aleixpol@...> wrote:

> You can easily check that using ldd.

If you want:

fraga@tux /usr/local/kde4/lib/kde4$ ldd kopete_wlm.so |grep msn
ldd: warning: you do not have execution permission for `./kopete_wlm.so'
libmsn.so.0.2 => /usr/local/lib/libmsn.so.0.2 (0x00007f07affe4000)

To confirm:

fraga@tux /usr/local/kde4/lib/kde4$ ls /usr/local/lib/libmsn.so* -lt
-rw-r--r-- 1 root root 785052 Nov 24 15:42 /usr/local/lib/libmsn.so.0.2.0
lrwxrwxrwx 1 root root 13 Nov 23 13:36 /usr/local/lib/libmsn.so -> libmsn.so.0.2
lrwxrwxrwx 1 root root 15 Nov 23 13:36 /usr/local/lib/libmsn.so.0.2 -> libmsn.so.0.2.0

So there's nothing wrong here. I use WLM since the first
version and I never had problem with it.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-25T18:54:27Z

You can easily check that using ldd.

It's useful to check the compilation line using "make VERBOSE=1"

Hope that helps :P

Aleix

On Wed, Nov 25, 2009 at 2:56 PM, Gustavo Boiko <gustavo.boiko@...> wrote:

On 24/11/2009, at 21:02, Lamarque Vieira Souza wrote:

> Em Terça-feira 24 Novembro 2009, Dâniel Fraga escreveu:
>> On Tue, 24 Nov 2009 16:38:11 -0200
>>
>> Lamarque Vieira Souza <lamarque@...> wrote:
>>> This is weird, if the #ifdef is resolving to false the error message
>>> should be different (like ‘inboxUrl’ was not declared in this scope). You
>>> can confirm if the #ifdef is resolving to true by adding this line inside
>>> the #ifdef:
>>
>> No. The #ifdef is resolving to true, but the reference
>>
>> remains undefined... See below:
>
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6:
>> warning: #warning Inside ifdef
>> (...)
>>
>> Everything is ok until:
>>
>> Linking CXX shared module ../../../lib/kopete_wlm.so
>> CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
>> `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
>> MSN::hotmailInfo)':
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
>> undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)' collect2:
>> ld returned 1 exit status
>> make[2]: *** [lib/kopete_wlm.so] Error 1
>> make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
>> make: *** [all] Error 2
>>
>> Really weird problem...
>
> I agree, it seems more and more like a bug in cpp or g++. One more test, try
> surrounding the newEmailNotification signal with the same #ifdef in
> wlmlibmsn.h to see if starts to have the same problem.

Very unlikely it is.

Dâniel, could you please rm -f /usr/local/lib/libmsn.so* and try building wlm again?
I'm suspecting it is linking to another libmsn somewhere else.

Cheers

Boiko

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-25T18:54:16Z

On Wed, 25 Nov 2009 11:56:45 -0200
Gustavo Boiko <gustavo.boiko@...> wrote:

> Very unlikely it is.
>
> Dâniel, could you please rm -f /usr/local/lib/libmsn.so* and try building wlm again?
> I'm suspecting it is linking to another libmsn somewhere else.

I already did that. You can bet there is no other libmsn.so
installed here. I completely removed the old one and installed a fresh
one.

I suggest we create a small c++ code with a ifdef to test if in
all cases the ifdef is causing this or not.... we could create a small
sample .cpp file with a .h and I would try to compile it here. If it
generates some error, I will report to gcc developers... it's the only
way I think...

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-25T18:49:10Z

On Tue, 24 Nov 2009 21:02:04 -0200
Lamarque Vieira Souza <lamarque@...> wrote:

> I agree, it seems more and more like a bug in cpp or g++. One more test, try
> surrounding the newEmailNotification signal with the same #ifdef in
> wlmlibmsn.h to see if starts to have the same problem.

Yes, same error:

Linking CXX shared module ../../../lib/kopete_wlm.so
CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function `Callbacks::gotNewEmailNotification(MSN::NotificationServerConnection*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::basic_string<char, std::char_traits<char>, std::allocator<char> >)':
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:571: undefined reference to `Callbacks::newEmailNotification(QString, QString)'
CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*, MSN::hotmailInfo)':
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581: undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)'
collect2: ld returned 1 exit status
make[2]: *** [lib/kopete_wlm.so] Error 1
make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
make: *** [all] Error 2

***

So it's clear that the #ifdef is causing this.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-25T05:56:45Z

On 24/11/2009, at 21:02, Lamarque Vieira Souza wrote:

> Em Terça-feira 24 Novembro 2009, Dâniel Fraga escreveu:
>> On Tue, 24 Nov 2009 16:38:11 -0200
>>
>> Lamarque Vieira Souza <lamarque@...> wrote:
>>> This is weird, if the #ifdef is resolving to false the error message
>>> should be different (like ‘inboxUrl’ was not declared in this scope). You
>>> can confirm if the #ifdef is resolving to true by adding this line inside
>>> the #ifdef:
>>
>> No. The #ifdef is resolving to true, but the reference
>>
>> remains undefined... See below:
>
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6:
>> warning: #warning Inside ifdef
>> (...)
>>
>> Everything is ok until:
>>
>> Linking CXX shared module ../../../lib/kopete_wlm.so
>> CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
>> `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
>> MSN::hotmailInfo)':
>> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
>> undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)' collect2:
>> ld returned 1 exit status
>> make[2]: *** [lib/kopete_wlm.so] Error 1
>> make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
>> make: *** [all] Error 2
>>
>> Really weird problem...
>
> I agree, it seems more and more like a bug in cpp or g++. One more test, try
> surrounding the newEmailNotification signal with the same #ifdef in
> wlmlibmsn.h to see if starts to have the same problem.

Very unlikely it is.

Dâniel, could you please rm -f /usr/local/lib/libmsn.so* and try building wlm again?
I'm suspecting it is linking to another libmsn somewhere else.

Cheers

Boiko
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

How to avoid a new incoming message to getting attached at the top of the chat window.!

2009-11-25T04:28:47Z

Hi,
I have a seperate branch of kopete, at "branches/work/soc-logging-framework/kopete" where I am working on the history plugin for logging into akonadi.
2 days back I found a bug, which I am unable to find what the root cause of it is.

The bug is as follows.
When there is an incoming message and the the no of lines of chat in our chat file(assume 3) is less than the value in our config(assume 7), then that new incoming message is getting attached at the top of the chat window.

While we have enough chats(no of lines of chat we have n the log is enough, assume 8) then that incoming message is attached at the end.
I am attaching screenshots , so that you can take a look.

I am unable to find out why is it working in once case, while not working on another.
I wonder if someone can throw some light on why this may be happening!

This problem is only in my modified plugin and not in the existing history plugin.
I have tried but haven't been able to figure out where the problem lies.

Screenshots are at the following link.
http://picpaste.com/kopete1.jpeg
http://picpaste.com/kopete2.jpeg

Thanks.

Re: [kopete-devel] Google Talk support in Kopete

2009-11-25T03:56:56Z

Hello,

it is my mistake. Now it is fixed on svn.

--
Pali Rohár
pali.rohar@...

On St 25. November 2009 10:33:13 Michael Zanetti wrote:

> Hi,
>
> I think here is something wrong. As Dâniel already pointed out it should be
> LIBORTP instead of LIBOTR.
>
> Note that libotr is an encryption library used by the OTR plugin while libortp
> is the Real-Time Transport library used for jingle phone calls.
>
> The ${LIBOTR_INCLUDE_DIR} in
> kopete/protocols/jabber/googletalk/libjingle/talk/session/phone/CMakeLists.txt
> should be removed or replaced by some ORTP includes.
>
> Michael
>
>
> On Monday 23 November 2009 19:42:16 Pali Rohár wrote:
> > On Ne 22. November 2009 14:22:36 Dâniel Fraga wrote:
> > > On Sun, 22 Nov 2009 10:13:00 +0100
> > >
> > > Pali Rohár <pali.rohar@...> wrote:
> > > > You can download and compile iLBC library for google libjingle using
> > > > this commands: $ wget
> > > > http://mirror.lihnidos.org/GNU/savannah/linphone/plugins/sources/msilbc
> > > >-2.0.0.tar.gz $ tar -xf msilbc-2.0.0.tar.gz
> > > > $ tar -xf msilbc-2.0.0/ilbc-rfc3951.tar.gz
> > > > $ cd ilbc-rfc3951
> > > > $ ./autogen.sh
> > > > $ autoreconf -i -f
> > > > $ ./configure --prefix=/usr --enable-shared=yes --enable-static=yes
> > > > $ make
> > > > $ sudo make install
> > > >
> > > > This works for me fine. You dont need msilbc but you need ilbc (it is
> > > > included in msilbc package).
> > >
> > > OK Pali, this worked perfectly here. Now just on trivial fix:
> > > libotr is essential for jingle support?
> >
> > Yes, you need libotr to build google libjingle.
> >
> > > CMake Error: The following variables are used in this project, but they
> > > are set to NOTFOUND.
> > > Please set them or make sure they are set and tested correctly in the
> > > CMake files:
> > > LIBOTR_INCLUDE_DIR
> > > used as include directory in
> > > directory
> > > /usr/local/src/svn/kdenetwork/kopete/protocols/jabber/googletalk/libjingl
> > >e/talk/session/phone
> > >
> > > -- Configuring incomplete, errors occurred!
> >
> > I fixed cmake files, checkout from svn and try build again.
> >
> > > ***
> > >
> > > My workaround is to just use a -DLIBOTR_INCLUDE_DIR= but if it
> > > is not essential, then it shouldn't demand it, right?sudo
> > >
> > > Thanks.
> >
>

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

signature.asc (204 bytes) Download Attachment

Re: [kopete-devel] Google Talk support in Kopete

2009-11-25T01:33:13Z

Hi,

I think here is something wrong. As Dâniel already pointed out it should be
LIBORTP instead of LIBOTR.

Note that libotr is an encryption library used by the OTR plugin while libortp
is the Real-Time Transport library used for jingle phone calls.

The ${LIBOTR_INCLUDE_DIR} in
kopete/protocols/jabber/googletalk/libjingle/talk/session/phone/CMakeLists.txt
should be removed or replaced by some ORTP includes.

Michael

On Monday 23 November 2009 19:42:16 Pali Rohár wrote:

> On Ne 22. November 2009 14:22:36 Dâniel Fraga wrote:
> > On Sun, 22 Nov 2009 10:13:00 +0100
> >
> > Pali Rohár <pali.rohar@...> wrote:
> > > You can download and compile iLBC library for google libjingle using
> > > this commands: $ wget
> > > http://mirror.lihnidos.org/GNU/savannah/linphone/plugins/sources/msilbc
> > >-2.0.0.tar.gz $ tar -xf msilbc-2.0.0.tar.gz
> > > $ tar -xf msilbc-2.0.0/ilbc-rfc3951.tar.gz
> > > $ cd ilbc-rfc3951
> > > $ ./autogen.sh
> > > $ autoreconf -i -f
> > > $ ./configure --prefix=/usr --enable-shared=yes --enable-static=yes
> > > $ make
> > > $ sudo make install
> > >
> > > This works for me fine. You dont need msilbc but you need ilbc (it is
> > > included in msilbc package).
> >
> > OK Pali, this worked perfectly here. Now just on trivial fix:
> > libotr is essential for jingle support?
>
> Yes, you need libotr to build google libjingle.
>
> > CMake Error: The following variables are used in this project, but they
> > are set to NOTFOUND.
> > Please set them or make sure they are set and tested correctly in the
> > CMake files:
> > LIBOTR_INCLUDE_DIR
> > used as include directory in
> > directory
> > /usr/local/src/svn/kdenetwork/kopete/protocols/jabber/googletalk/libjingl
> >e/talk/session/phone
> >
> > -- Configuring incomplete, errors occurred!
>
> I fixed cmake files, checkout from svn and try build again.
>
> > ***
> >
> > My workaround is to just use a -DLIBOTR_INCLUDE_DIR= but if it
> > is not essential, then it shouldn't demand it, right?sudo
> >
> > Thanks.
>

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

signature.asc (205 bytes) Download Attachment

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T15:02:04Z

Em Terça-feira 24 Novembro 2009, Dâniel Fraga escreveu:

> On Tue, 24 Nov 2009 16:38:11 -0200
>
> Lamarque Vieira Souza <lamarque@...> wrote:
> > This is weird, if the #ifdef is resolving to false the error message
> > should be different (like ‘inboxUrl’ was not declared in this scope). You
> > can confirm if the #ifdef is resolving to true by adding this line inside
> > the #ifdef:
>
> No. The #ifdef is resolving to true, but the reference
>
> remains undefined... See below:

> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6:
> warning: #warning Inside ifdef
> (...)
>
> Everything is ok until:
>
> Linking CXX shared module ../../../lib/kopete_wlm.so
> CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
> `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
> MSN::hotmailInfo)':
> /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
> undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)' collect2:
> ld returned 1 exit status
> make[2]: *** [lib/kopete_wlm.so] Error 1
> make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
> make: *** [all] Error 2
>
> Really weird problem...

I agree, it seems more and more like a bug in cpp or g++. One more test, try
surrounding the newEmailNotification signal with the same #ifdef in
wlmlibmsn.h to see if starts to have the same problem.

--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T13:20:57Z

On Tue, 24 Nov 2009 16:38:11 -0200
Lamarque Vieira Souza <lamarque@...> wrote:

> This is weird, if the #ifdef is resolving to false the error message should
> be different (like ‘inboxUrl’ was not declared in this scope). You can confirm
> if the #ifdef is resolving to true by adding this line inside the #ifdef:

No. The #ifdef is resolving to true, but the reference
remains undefined... See below:

> #warning Inside ifdef
>
> and search for a line like this in make's output:

As you suggested, the code is the following:

#ifdef LIBMSN_INBOX_URL_ENABLED
#warning Inside ifdef
void
inboxUrl(MSN::hotmailInfo & info);
#endif

As you can see the warning is there:

[ 91%] Building CXX object kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/wlmaccount.o
In file included from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmserver.h:20,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmaccount.h:24,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmaccount.cpp:17:
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6: warning: #warning Inside ifdef
In file included from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmserver.h:20,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmaccount.h:24,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmprotocol.cpp:18:
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6: warning: #warning Inside ifdef
In file included from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmserver.h:20,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmaccount.h:24,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp:33:
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6: warning: #warning Inside ifdef
In file included from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmserver.h:20,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmaccount.h:24,
from /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmcontact.cpp:36:
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:463:6:
warning: #warning Inside ifdef
(...)

Everything is ok until:

Linking CXX shared module ../../../lib/kopete_wlm.so
CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*, MSN::hotmailInfo)':
/home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581: undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)'
collect2: ld returned 1 exit status
make[2]: *** [lib/kopete_wlm.so] Error 1
make[1]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
make: *** [all] Error 2

Really weird problem...

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T10:38:11Z

Em Terça-feira 24 Novembro 2009, Dâniel Fraga escreveu:

> On Tue, 24 Nov 2009 14:07:38 -0200
>
> Lamarque Vieira Souza <lamarque@...> wrote:
> > I do not think that is the problem, if LIBMSN_INBOX_URL_ENABLED is not
> > defined when including wlmlibmsn.h the error message would be different.
> > The linker thinks inboxUrl is a class method, not a signal, that is the
> > problem. Dâniel, could you try recompiling again now just removing the
> > #ifdef LIBMSN_INBOX_URL_ENABLED and the #endif but keeping inboxUrl at
> > the same place (after newMailNotification signal). If it does not work,
> > try adding a fake
>
> Ok, I tried that (removing the #ifdef) and it worked.
>
> > signal after inboxUrl to see what happens. I still think it is a
> > compiler/liker bug, we need more test to figure out what is really
> > happening.
>
> So the whole problem is with the #ifdef? I mean, the "parser"
> is not recognizing the ifdef and generates the error message?

This is weird, if the #ifdef is resolving to false the error message should
be different (like ‘inboxUrl’ was not declared in this scope). You can confirm
if the #ifdef is resolving to true by adding this line inside the #ifdef:

#warning Inside ifdef

and search for a line like this in make's output:

protocols/wlm/wlmlibmsn.h:463:2: warning: #warning Inside ifdef

> Would it worth to write a small sample code to test those ifdef
> statements? If so, and if it's really a compiler bug we could send to
> gcc developers...

#ifdef is a pre-processor statment, not compiler's, we need to know if the
problem is in the pre-processor (cpp command) or in the compiler (g++
command).

--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T10:01:21Z

On Tue, 24 Nov 2009 14:07:38 -0200
Lamarque Vieira Souza <lamarque@...> wrote:

> I do not think that is the problem, if LIBMSN_INBOX_URL_ENABLED is not
> defined when including wlmlibmsn.h the error message would be different. The
> linker thinks inboxUrl is a class method, not a signal, that is the problem.
> Dâniel, could you try recompiling again now just removing the #ifdef
> LIBMSN_INBOX_URL_ENABLED and the #endif but keeping inboxUrl at the same place
> (after newMailNotification signal). If it does not work, try adding a fake

Ok, I tried that (removing the #ifdef) and it worked.

> signal after inboxUrl to see what happens. I still think it is a
> compiler/liker bug, we need more test to figure out what is really happening.

So the whole problem is with the #ifdef? I mean, the "parser"
is not recognizing the ifdef and generates the error message?

Would it worth to write a small sample code to test those ifdef
statements? If so, and if it's really a compiler bug we could send to
gcc developers...

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T08:07:38Z

Em Terça-feira 24 Novembro 2009, Tiago Salem Herrmann escreveu:

> Dâniel Fraga wrote:
> > On Tue, 24 Nov 2009 10:27:41 -0200
> >
> > Tiago Salem Herrmann <salem@...> wrote:
> >> please, enter the libmsn build directory and check the following file:
> >> msn/config.h
> >> The macro should be defined. (I believe it is, or kopete would not fail
> >> to link)
> >
> > config.h:
> >
> > #ifndef LIBMSN_CONFIG_H
> > #define LIBMSN_CONFIG_H
> >
> > #define LIBMSN_INBOX_URL_ENABLED
> >
> > #endif
> >
> >> Could you please run "make clean; make VERBOSE=1" in wlm and paste the
> >> output on pastebin?
> >
> > Ok:
> >
> > http://pastebin.com/m360c253d
>
> hm, ok.
> one more try:
>
> rm /usr/local/include/msn -rf
> then compile libmsn again. Maybe a config.h is being included from
> outside the build directory.

I do not think that is the problem, if LIBMSN_INBOX_URL_ENABLED is not
defined when including wlmlibmsn.h the error message would be different. The
linker thinks inboxUrl is a class method, not a signal, that is the problem.
Dâniel, could you try recompiling again now just removing the #ifdef
LIBMSN_INBOX_URL_ENABLED and the #endif but keeping inboxUrl at the same place
(after newMailNotification signal). If it does not work, try adding a fake
signal after inboxUrl to see what happens. I still think it is a
compiler/liker bug, we need more test to figure out what is really happening.

--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T07:49:20Z

On Tue, 24 Nov 2009 12:06:28 -0200
Tiago Salem Herrmann <salem@...> wrote:

> hm, ok.
> one more try:
>
> rm /usr/local/include/msn -rf
> then compile libmsn again. Maybe a config.h is being included from
> outside the build directory.

Ok, I did that but the config.h file is installed the same way
with the same content.

> paste here "ls -la /usr/local/lib/libmsn.so" too.

lrwxrwxrwx 1 root root 13 Nov 23 13:36 /usr/local/lib/libmsn.so -> libmsn.so.0.2

You can be sure I completely removed any old libmsn... I just have the latest
svn installed...

Anyway, I can keep doing whatever tests you want until we find
the source of the problem. Thanks again.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T06:06:28Z

Dâniel Fraga wrote:

> On Tue, 24 Nov 2009 10:27:41 -0200
> Tiago Salem Herrmann <salem@...> wrote:
>
>
>> please, enter the libmsn build directory and check the following file:
>> msn/config.h
>> The macro should be defined. (I believe it is, or kopete would not fail
>> to link)
>>
>
> config.h:
>
> #ifndef LIBMSN_CONFIG_H
> #define LIBMSN_CONFIG_H
>
> #define LIBMSN_INBOX_URL_ENABLED
>
> #endif
>
>
>> Could you please run "make clean; make VERBOSE=1" in wlm and paste the
>> output on pastebin?
>>
>
> Ok:
>
> http://pastebin.com/m360c253d
>
>

hm, ok.
one more try:

rm /usr/local/include/msn -rf
then compile libmsn again. Maybe a config.h is being included from
outside the build directory.

paste here "ls -la /usr/local/lib/libmsn.so" too.

Thanks.
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T05:55:02Z

On Tue, 24 Nov 2009 10:27:41 -0200
Tiago Salem Herrmann <salem@...> wrote:

> please, enter the libmsn build directory and check the following file:
> msn/config.h
> The macro should be defined. (I believe it is, or kopete would not fail
> to link)

config.h:

#ifndef LIBMSN_CONFIG_H
#define LIBMSN_CONFIG_H

#define LIBMSN_INBOX_URL_ENABLED

#endif

> Could you please run "make clean; make VERBOSE=1" in wlm and paste the
> output on pastebin?

Ok:

http://pastebin.com/m360c253d

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-24T04:27:41Z

Dâniel Fraga wrote:

> On Mon, 23 Nov 2009 20:21:02 -0200
> Lamarque Vieira Souza <lamarque@...> wrote:
>
>
>> That was only a test, it seems g++ 4.4.2 has problems to compile this code.
>> Could you undo all the changes (or checkout wlmlibmsn.h again) and verify if
>> it still compiles? Do you use some kind of compiler cache like ccache?
>>
>
> No, I don't use any kind of cache, just the plain gcc/g++.
>
> If it's a compiler issue, at least it is interesting ;)
>
> Let's go:
>
> fraga@tux ~/svn/kdenetwork$ rm kopete/protocols/wlm/wlmlibmsn.h
> rm: remove regular file `kopete/protocols/wlm/wlmlibmsn.h'? y
> fraga@tux ~/svn/kdenetwork$ ./svn.sh
> Restored 'kopete/protocols/wlm/wlmlibmsn.h'
> At revision 1053388.
> At revision 1053386.
>
> Tried to compile and got the same error again:
>
> CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
> `Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
> MSN::hotmailInfo)': /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
> undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)'
> collect2: ld returned 1 exit status
>
> I'd like to ask you the following: if your suggested "test"
> worked, so can we say that it's a compiler issue or not necessarily?
>
> Thanks.
>
> Ps: if it's a compiler issue, I can compile some test program
> here (you provide the code). If it doesn't work as expected we can talk
> to gcc folks. Anyway, I can do any test you want.
>
>

My gcc is 4.4.1 and works fine.

please, enter the libmsn build directory and check the following file:
msn/config.h
The macro should be defined. (I believe it is, or kopete would not fail
to link)

Could you please run "make clean; make VERBOSE=1" in wlm and paste the
output on pastebin?

Thanks.
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T15:57:41Z

On Mon, 23 Nov 2009 20:21:02 -0200
Lamarque Vieira Souza <lamarque@...> wrote:

> That was only a test, it seems g++ 4.4.2 has problems to compile this code.
> Could you undo all the changes (or checkout wlmlibmsn.h again) and verify if
> it still compiles? Do you use some kind of compiler cache like ccache?

No, I don't use any kind of cache, just the plain gcc/g++.

If it's a compiler issue, at least it is interesting ;)

Let's go:

fraga@tux ~/svn/kdenetwork$ rm kopete/protocols/wlm/wlmlibmsn.h
rm: remove regular file `kopete/protocols/wlm/wlmlibmsn.h'? y
fraga@tux ~/svn/kdenetwork$ ./svn.sh
Restored 'kopete/protocols/wlm/wlmlibmsn.h'
At revision 1053388.
At revision 1053386.

Tried to compile and got the same error again:

CMakeFiles/kopete_wlm.dir/wlmlibmsn.o: In function
`Callbacks::gotInboxUrl(MSN::NotificationServerConnection*,
MSN::hotmailInfo)': /home/fraga/svn/kdenetwork/kopete/protocols/wlm/wlmlibmsn.cpp:581:
undefined reference to `Callbacks::inboxUrl(MSN::hotmailInfo&)'
collect2: ld returned 1 exit status

I'd like to ask you the following: if your suggested "test"
worked, so can we say that it's a compiler issue or not necessarily?

Thanks.

Ps: if it's a compiler issue, I can compile some test program
here (you provide the code). If it doesn't work as expected we can talk
to gcc folks. Anyway, I can do any test you want.

--
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: cmake in kdenetwork/kopete/protocols (jingle)

2009-11-23T14:28:05Z

On Monday 23 November 2009, Alexander Neundorf wrote:
...
> I (together with Volker Krause and some some BSD guys) are currently trying
> to get nightly builds for several KDE modules running at my.cdash.org.
> There is also a nightly build for kdenetwork. It is done on my personal
> machine with cmake 2.6.2. If this breaks (e.g. because something which is
> not supported by 2.6.2 is used) we will notice this just the next day. If
> you want to get email notification in that case, go to my.cdash.org (hosted
> by Kitware), get a login, and subscribe to the kdenetwork project.

Here we have it:
http://my.cdash.org/index.php?project=kdenetwork&date=2009-11-22
http://my.cdash.org/viewConfigure.php?buildid=38632

Urs, if you are the kdenetwork maintainer, I suggest you get a login on
my.cdash.org and subscribe to the kdenetwork project.

Alex
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T14:21:02Z

Em Segunda-feira 23 Novembro 2009, Dâniel Fraga escreveu:

> On Mon, 23 Nov 2009 22:34:54 +0100
>
> Pau Garcia i Quiles <pgquiles@...> wrote:
> > No. It was set to OFF by default in libmsn 4.0 beta7 because Thiago
> > thought that way libmsn would remain binary compatible with beta6 and
> > older. Unfortunately, he also introduced a few data members, which
> > broke binary compatibility. It seems I (the Debian maintainer for
> > libmsn) was the only one who noticed this issue. So there is no point
> > in setting LIBMSN_INBOX_URL_ENABLED to OFF.
>
> Ok. So to make it very clear: I *never* *ever* touched this
> option ;). I know this option is being discussed here, but I even
> didn't know it exist.

I think Garcia was talking to Tiago about this one, not you.

> So the only "solution" or "workaround" for now was the one
> provided by Lamarque Vieira Souza. In other words, to remove the #ifdef
> and put it before newEmailNotification. That's the only thing that
> worked here.

That was only a test, it seems g++ 4.4.2 has problems to compile this code.
Could you undo all the changes (or checkout wlmlibmsn.h again) and verify if
it still compiles? Do you use some kind of compiler cache like ccache?

--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T13:46:37Z

On Mon, 23 Nov 2009 22:34:54 +0100
Pau Garcia i Quiles <pgquiles@...> wrote:

> No. It was set to OFF by default in libmsn 4.0 beta7 because Thiago
> thought that way libmsn would remain binary compatible with beta6 and
> older. Unfortunately, he also introduced a few data members, which
> broke binary compatibility. It seems I (the Debian maintainer for
> libmsn) was the only one who noticed this issue. So there is no point
> in setting LIBMSN_INBOX_URL_ENABLED to OFF.

Ok. So to make it very clear: I *never* *ever* touched this
option ;). I know this option is being discussed here, but I even
didn't know it exist.

So the only "solution" or "workaround" for now was the one
provided by Lamarque Vieira Souza. In other words, to remove the #ifdef
and put it before newEmailNotification. That's the only thing that
worked here.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T13:34:54Z

On Mon, Nov 23, 2009 at 9:29 PM, Dâniel Fraga <fragabr@...> wrote:
> On Mon, 23 Nov 2009 17:27:51 -0200
> Lamarque Vieira Souza <lamarque@...> wrote:
>
>> Thiago added that option to libmsn to make sure no one would break binary
>> compatibility with old libmsn by accident. That option is supposed to be off
>> by default unless Thiago has changed that in newer libmsn versions.
>
> Ok, but I notice here by default it's always ON. Should I
> explictly declare it as OFF?

No. It was set to OFF by default in libmsn 4.0 beta7 because Thiago
thought that way libmsn would remain binary compatible with beta6 and
older. Unfortunately, he also introduced a few data members, which
broke binary compatibility. It seems I (the Debian maintainer for
libmsn) was the only one who noticed this issue. So there is no point
in setting LIBMSN_INBOX_URL_ENABLED to OFF.

--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T12:29:55Z

On Mon, 23 Nov 2009 17:27:51 -0200
Lamarque Vieira Souza <lamarque@...> wrote:

> Thiago added that option to libmsn to make sure no one would break binary
> compatibility with old libmsn by accident. That option is supposed to be off
> by default unless Thiago has changed that in newer libmsn versions.

Ok, but I notice here by default it's always ON. Should I
explictly declare it as OFF?

> That is pretty young, maybe it is a compiler bug. Has anyone else able to
> compile Kopete with g++ 4.4.2? I use 4.3.4 here. Which distribution do you
> use? As a test could you try moving inboxUrl declaration in wlmlibmsn.h to
> before newEmailNotification declaration and remove the #ifdef
> LIBMSN_INBOX_URL_ENABLED and the #endif?

My distribution is like Linux from scratch. I like to test new
things, compile all by myself. But I never had problem compiling Kopete
(and WLM) until now.

I tried your suggestion and it solved the issue. It compiled
perfectly.

--
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: cmake in kdenetwork/kopete/protocols (jingle)

2009-11-23T12:27:34Z

On Monday 23 November 2009, Urs Wolfer wrote:

> On Monday 23 November 2009 13:32:27 Raphael Kubo da Costa wrote:
> > On Monday 23 November 2009 10:15:36 Jussi Kekkonen wrote:
> > > 2009/11/23 Pali Rohár <pali.rohar@...>:
> > > > Hello,
> > > >
> > > > I have cmake version 2.6-patch 4 (standard version in Kubuntu Karmic
> > > > 9.10) and I can compile kopete with google libjingle support without
> > > > any problems.
> > >
> > > Good to hear, I'm on bit older release myself.
> > >
> > > >> But with those commits, you did changes that apparently requires
> > > >> cmake newer than anywhere else in KDE, as everywhere else 2.6.2 is
> > > >> minimum required and now Kopete compiles only with versions 2.8 and
> > > >> up (correct me if I'm wrong).
> > >
> > > Indeed, I was wrong, it's 2.6.3 which does support this:
> > > http://www.cmake.org/files/v2.6/CMakeChangeLog-2.6.4 "- Add
> > > parenthetical expressions to if" in "Changes in CMake 2.6.3 RC 4"
> > >
> > > Now it's narrowed down, should the version requirement be pumped up or
> > > fixed expressions to support same version than rest of KDE does?
> > > For example 2.6.2 is mentioned in here:
> > > http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites#CMake
> >
> > I'm not sure if the CMake >= 2.6.2 policy applies only to kdelibs; in
> > this case, it'd be good to ask the kdenetwork module maintainer, Urs
> > Wolfer, added in CC.
>
> I prefer to have the same minimum requirements as kdelibs does have.

Yes, definitely. Because otherwise everybody who wants to compile complete KDE
trunk needs the version you require in kdenetwork.

> Alexander, what do you think? Bump it in kdelibs?

Is the only reason the parenthesis ?
I think that's not worth requiring everybody to upgrade his cmake version.
Everytime cmake is upgraded there are big complaints that this happens already
again, and I really think just having the parenthesis is not enough for that.

> Require an older CMake version in kdenetwork?

Well, 2.6.2 I'd say.

I (together with Volker Krause and some some BSD guys) are currently trying to
get nightly builds for several KDE modules running at my.cdash.org.
There is also a nightly build for kdenetwork. It is done on my personal
machine with cmake 2.6.2. If this breaks (e.g. because something which is not
supported by 2.6.2 is used) we will notice this just the next day.
If you want to get email notification in that case, go to my.cdash.org (hosted
by Kitware), get a login, and subscribe to the kdenetwork project.

Alex
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: WLM trivial compilation issue (Callbacks::inboxUrl(MSN::hotmailInfo&))

2009-11-23T12:10:14Z

On Mon, Nov 23, 2009 at 8:27 PM, Lamarque Vieira Souza
<lamarque@...> wrote:

> Em Segunda-feira 23 Novembro 2009, Dâniel Fraga escreveu:
>> On Mon, 23 Nov 2009 16:10:51 -0200
>>
>> Lamarque Vieira Souza <lamarque@...> wrote:
>> > LIBMSN_INBOX_URL_ENABLED is enabled or g++ would not even try to compile
>> > line 581. LIBMSN_INBOX_URL_ENABLED is defined in
>> > /usr/include/msn/config.h (one of
>>
>> Ok, but I just said that I never used that option. I mean, if
>> it's default, I was not aware of it.
>
> Thiago added that option to libmsn to make sure no one would break binary
> compatibility with old libmsn by accident. That option is supposed to be off
> by default unless Thiago has changed that in newer libmsn versions.

It's ON by default in libmsn 4.0.

Actually, Tiago accidentally broken binary compatibility in beta7 by
adding a few data members, regardless of what you do with
LIBMSN_INBOX_URL_ENABLED.

The binary compatiblity chart would be something like this:

* libmsn 4.0 beta6 is binary-compatible with libmsn 4.0 <= beta6

* libmsn 4.0 beta7 with LIBMSN_INBOX_URL_ENABLED = OFF is binary
compatible with libmsn 4.0 beta7 with LIBMSN_INBOX_URL_ENABLED = OFF
and libmsn 4.0 beta8 with LIBMSN_INBOX_URL_ENABLED = OFF. It is NOT
binary compatible with libmsn 4.0 final.

* libmsn 4.0 beta7 with LIBMSN_INBOX_URL_ENABLED = ON is binary
compatible with libmsn 4.0 >= beta7 with LIBMSN_INBOX_URL_ENABLED =
ON, including libmsn 4.0 final.

--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel

Re: Google Talk support in Kopete

2009-11-23T11:55:54Z

On Mon, 23 Nov 2009 19:42:16 +0100
Pali Rohár <pali.rohar@...> wrote:

> Yes, you need libotr to build google libjingle.

You mean libortp, not libotr right? Because I built libjingle
without libotr.

--
Linux 2.6.31: Man-Eating Seals of Antiquity

_______________________________________________
kopete-devel mailing list
kopete-devel@...
https://mail.kde.org/mailman/listinfo/kopete-devel