view libpurple/protocols/silc/README @ 24389:2b62300d2c19

Use libtool to build static archives when --with-static-prpls is passed to configure. Does anyone know why we weren't using libtool before? We were building old-fashioned .a files. But libtool archives (.la) can contain either static or shared libraries. I found it a lot easier to get static prpl compilation working after making this change (that is to say, it worked). Without this I got this error, which is probably fixable, but consistently using libtool seems like it makes things easier: *** Warning: Linking the shared library libpurple.la against the *** static library ../libpurple/protocols/msn/libmsn.a is not portable! /usr/bin/ld: ../libpurple/protocols/msn/libmsn.a(libmsn_a-msn.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../libpurple/protocols/msn/libmsn.a: could not read symbols: Bad value collect2: ld returned 1 exit status

SILC Purple Plugin
==================

This is the Purple protocol plugin of the protocol called Secure Internet
Live Conferencing (SILC).  The implementation will use the SILC Toolkit,
freely available from the http://silcnet.org/ site, for the actual SILC
protocol implementation.

To include SILC into Purple, one needs to first compile and install
the SILC Toolkit.  It is done as follows:

	./configure
	make
	make install

This will compile shared libraries of the SILC Toolkit.  If the --prefix
is not given to ./configure, the binaries are installed into the
/usr/local/silc directory.

Once the Toolkit is installed one needs to tell Purple's ./configure
script where the SILC Toolkit is located.  It is done as simply as:

	./configure

if pkg-config is installed in your system.  If it is isn't it's done as:

	./configure --with-silc-libs=/path/to/silc/lib
		    --with-silc-includes=/path/to/silc/include

If the SILC Toolkit cannot be found then the SILC protocol plugin will
not be compiled.