libpurple in xcode

[kelo]

Hey,

there used to be a xcodeproj with libpurple in svn. Where did it go? I found it rather usefull to develop and debug libpurple on a mac.

[evands]

see the README file in adium/Utilities/dep-build-scripts for the new libpurple build process.

[kelo]

I see. But i was asking if it is possible to build libpurple inside XCode for debugging use. Or should I rather use linux for libpurple develoment?

[evands]

I still don't understand your question. The file above explains how to build libpurple for Adium, including its dependencies, and how to subsequently package it to libpurple.framework. If you're trying to build libpurple for other purposes, there's no reason the same process wouldn't work for you... and of course you could just run configure and make in your pidgin source folder to build just libpurple.

[kelo]

Ok, let me rephrase my question: I want to participate in libpurple development. What should I do as a Mac user?

[evands]

Ok, let me rephrase my question: I want to participate in libpurple development. What should I do as a Mac user?

Ah!

You have multiple choices. You can use Adium as your UI for libpurple development, which simply means following the instructions as described in the README. Point your PIDGIN_SOURCE directory to your development pidgin repository, make changes to libpurple there, then use the Adium scripts to build libpurple and copy it to the appropriate places.

You can install the various dependencies for Pidgin or for Finch and use those UIs. In that case, you use the build process as you normally would for Pidgin or Finch or both. You'll need X11 installed for Pidgin (installer is on your Mac OS X install disks).

[daqula]

I have tried what the README said.. but got failed.

the first fail, I got one compile error during make libpurple
but after that fail, I always got fain in libpurple configure.. the error log is:
"
configure: error:

The msgfmt command is required to build libpurple. If it is installed
on your system, ensure that it is in your path. If it is not, install
GNU gettext to continue.

If you have msgfmt installed, but for some reason this error message
is still displayed, you have encountered what appears to be a bug in
third-party configure macros. Try setting the MSGFMT environment
variable to the absolute path to your msgfmt binary and trying
configure again, like this:

MSGFMT=/path/to/msgfmt ./configure ...
"
could you help me on this?
thanks

[evands]

You're running the purple_make.sh script after running the previous ones as specified in the README?

[daqula]

hi,
after some digging, seems found the reason why compile failed.
the compile error I got is
"...jabber/auth.c:393: error: ‘struct _JabberStream’ has no member named ‘current_mech’
"
the original libpurple code does not contain the 'current_mesh' in in auth.c, it is from patchs
"./libpurple_jabber_avoid_sasl_option_hack.diff" and "libpurple_jabber_use_builtin_digestmd5.diff".
since patchs bring current_mech up, why it didn't patch jabber.h either?(which contains the definition of _JabberStream)


another question, from the README that these scripts target for 2.3.1, but the adium contains libpurple framework target for 2.4.1, I am little bit confused here, is it for 2.3.1?

-daqula

[evands]

README was lying. Check it agin as of [23353] or later.