| 25 | | To cut a long story short, however, follow the brief HOWTO in the UsingPidginMonotone, but substitute "im.pidgin.pidgin" for "im.pidgin.soc.2008.vv", and of course "/user/" for whatever your own user is, to make things come out as a subdirectory of your own home directory, and to make sure you get the right development 'branch' of the source 'tree'. |
| 26 | | |
| 27 | | The HOWTO will end you up in the $DATABASE directory when you need to be in the $WORKINGDIR directory to see the code that monotone has downloaded, so "cd $WORKINGDIR" afterwards. |
| 28 | | |
| 29 | | (This done it is probably a very good idea (tm) to suggest that you force the install location of the development version you are about to build to be under /usr/local/ or /opt/ instead of in with the system software so as to avoid it nuking a working version of Pidgin you might have installed from a package!--exec-prefix and --prefix options to the './configure' command! ) |
| 30 | | |
| 31 | | And then the related comments in [http://developer.pidgin.im/wiki/Installing%20Pidgin#IhavethesourcehowdoIbuildthisthing HowDoIBuildThisThing]. You'll probably find that you need autoconf/aclocal/automake packages installed for that to work though. With that covered, I refer back to the original author's comments(/Kyrian)... |
| | 22 | For help with building, see [http://developer.pidgin.im/wiki/Installing%20Pidgin#Compiling Compiling Pidgin]. Please carefully read through that section and any extra information for the distribution you're using. |
| 69 | | (Maiku) |
| 70 | | It looks like the farsight package (and farsight-devel) listed is Farsight 1, whereas Farsight 2 is required. |
| 71 | | |
| 72 | | (Kyrian) |
| 73 | | Maiku is quite right, these will need building from source, download from here: http://farsight.freedesktop.org/releases/farsight2/ |
| 74 | | |
| 75 | | I'll see if I can create a .src.rpm for it and plonk it somewhere for download. |
| 76 | | |
| 77 | | You will need to be running Fedora Core 9 or a custom-built version of the base 'gstreamer' package in order to build and/or utilise the farsight2 libraries. (FC8 version is too old at 0.10.15, but FC9 is ok on 0.10.19). |
| 78 | | (/Kyrian) |
| 79 | | |
| 80 | | These come from Fedora base repos, and one from the Livna repo, in my setup. There are about twice as many packages again required for dependencies, but they come from the Fedora repo, so there should not be any problem caused by that. |
| 81 | | |
| 82 | | Of course, you'll also need a client for the Monotone system installed for the above UsingPidginMonotone commands to work, these come from the 'monotone' package, which again can be easily installed using Yum. |
| 83 | | |
| 84 | | For actual building, you'll need to install a variety of '*-devel' packages in order to get past the './configure' stage, but I am going to assume these are detailed elsewhere, and that the reader has enough experience to work this out for themselves. |
| 85 | | |
| 86 | | The requirement for the "avahi-glib-devel", and (possibly also) "libgpg-error-devel" packages to be installed are a bit of a curve ball that you might miss though? |
| 87 | | |
| 88 | | Using the basic configure line from a .src.rpm of pidgin from Fedora (in /usr/src/redhat/SPECS/pidgin.spec) will get Pidgin to build, provided you have the pre-requisites. The mandatory parts of the FC spec file's configure line for pidgin are: |
| 89 | | |
| 90 | | ./configure --enable-gnutls=no --enable-nss=yes --enable-cyrus-sasl --enable-tcl --enable-tk --disable-schemas-install |
| 91 | | |
| 92 | | And then there are optional args which I am not so sure about. |
| 93 | | |
| 94 | | The following commandline may prove useful for configuration if you do it another way (that's as far as I really got): |
| 95 | | |
| 96 | | AVAHI_CFLAGS=-I/usr/include/avahi-glib ./configure --with-avahi-client-includes=/usr/include/avahi-client |
| 97 | | |
| 98 | | [ More later. I don't think the above compile will actually enable Maiku's code by default? Can't be *that* easy? Indeed, a quick 'ldd' on various stuff installed by the build process shows no sign of being linked to the farsight libs! The config.log file also shows a failure to find farsight2 which explains it ;-) ] |
| | 60 | * [http://farsight.freedesktop.org/releases/farsight2/ farsight2-0.10] |
