Hi Ralf,

Ralf Schlatterbeck wrote:
> We'd like to integrate a newer version of limgaim (for instant messaging
> with most protocols except sip) into qutecom. The current version
> shipped is so old that we think many bugs we're seeing stem from this
> old version. Is there a technical reason for including this lib with
> qutecom?

There were some issues when we upgraded from libgaim 2.0b1 to 2.0b6, and
again when we upgraded to libpurple. Both these upgrades were more or
less completed though.

It looks like you're building off an older branch (the 2.1 branch,
perhaps?) rather than where the active development was happening in
Wengo, the 2.2 branch. You should have a look at the libpurple
integration there.

> Our idea would be to use an external lib (not ship the library with
> qutecom).

You can - the only change that was made to libgaim is, as I understand
it, an interface to set the presence and status message for all
configured protocols to the same setting. If Julien Bossart is still on
the list, perhaps he can give you more details.

> But my knowledge of the build-system is too small to make this change.
> Can you point us in the direction where to look for necessary changes in
> the build-system?

There is lots of documentation on CMake and owbuild in the old OpenWengo
wiki (please keep this resource when migrating to qutecom!): a starting
point might be
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/OWBuild and the
links cited there to the CMake documentation.

> Related: Does libgaim compile under windows or is the reason to ship
> libgaim with qutecom that there are changes to the original libs?

libgaim does compile under windows. There were issues that I never
really investigated - the process for generating Windows binaries wasn't
what interested me most in the project, to be honest, even if I felt it
was vital to have them.

Cheers,
Dave.

-- 
Dave Neary
[EMAIL PROTECTED]
Tel: +33 9 51 13 46 45
Cell: +33 6 77 01 92 13
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to