brazerzkidailiving.blogg.se

Pidgin for mac for mac os x#
Pidgin for mac for mac os#
Pidgin for mac mac os x#
Pidgin for mac install#

Of course, the “–prefix” is optional it will install Pidgin in /usr/local/bin otherwise. configure -prefix=$HOME/.local -without-x -enable-gtkstatusicon -disable-gestures Get the Pidgin source, and get the patch from this ticket, and compile Pidgin with

Pidgin for mac for mac os#

Wow, GTK on the Mac, natively… thanks, folks who brought us Gtk+ for Mac OS X! To test this, try the following:Īll should work. You should now have “GTK+ Mac OS X” installed. In my case, everything went fine (except for one minor error, where I picked “ignore error and continue” from the options it gave). I suspect I built a couple of modules more than once feel free to remove meta-gtk-osx-core from the second build command, for example. Of course, most of that is redundant, but I had disk space to spare, and pygtk to try out. Jhbuild build meta-gtk-osx-core meta-gtk-osx-python meta-gtk-osx-themes gossip Then, make sure ~/bin is in your $PATH, and: It is possible to change this, but I remember having run into trouble during an earlier attempt doing so, so I didn’t touch anything this time.ĭownload this file, and save it as ~/.jhbuildrc. Note that this installs jhbuild in ~/bin. Old instructions follow, mainly because I’m too lazy to delete them, but also in case someone does not want to use MacPorts or something: If you plan to script Pidgin using D-Bus, you could also do, before Step 1: sudo port install dbus-python25 If you would like to help debug them, checkout the project from svn- svn checkout I think-and/or file bugs/patches at the bug tracker.) ( Note: The pidgin-macosx from Sourceforge may be at a older version than the MacPorts version. Step 1: sudo port install pidgin +quartz +no_x11 Step 0: Install MacPorts, if you haven’t got it already. If you’re using MacPorts: For something which has had fewer changes from the original Pidgin, you can install it through MacPorts: dmg file from pidgin-macosx on Sourceforge, and double click on the Pidgin application. One-step simple way: All you have to do is download the. And maybe I can take a little credit for small improvements here and there, and nagging people into making certain changes :-))

(And of course, the Pidgin developers for writing Pidgin, and Richard Hult from Imendio AB for GTK+OSX.

Pidgin for mac mac os x#

Installing Pidgin on Mac OS X is now as simple as installing any other Mac OS X application, thanks to a train of effort from many people, starting with Anders Hasselqvist (“nevil”) for writing the patch with the gtkstatusicon implementation, Thomas Reifferscheid (reiffert) for including it on MacPorts, and finally Albert Zeyer for building it with Xcode and the GTK framework and making a. This is very simple to do and requires only one step, described below.

Pidgin for mac for mac os x#

Install Pidgin to run on the Mac desktop directly (without X11), using native GTK+ for Mac OS X and some minor modifications to Pidgin.

It is cumbersome, and I would not recommend it unless you are already doing much of your work inside X11 for some reason. However, using an X11 app on OS X is really like entering another universe entirely… it’s like having two entirely disjoint OSes that just happen to run simultaneously. Any default distribution of Pidgin should build fine on this, as long as you have all the dependencies installed. On the other hand, if you, like me, have tried Adium and have reasons for finding it unusable, then it is possible to install Pidgin on OS X too. Being a native Cocoa application, it is more well-integrated with the Mac desktop than a GTK-using application like Pidgin can ever be. It has several popular features such as message styles, and uses the Cocoa API native to Mac OS X, and all round looks pretty.

So you’re on Mac OS X, and want to use Pidgin on it.įirst: Why not use Adium? Adium is a Free multi-protocol IM client for Mac OS X that uses libpurple, the IM library that was developed as part of Pidgin.