view libpurple/plugins/perl/common/MANIFEST @ 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

Account.xs
AccountOpts.xs
BuddyIcon.xs
BuddyList.xs
Cipher.xs
Cmds.xs
Connection.xs
Conversation.xs
Debug.xs
FT.xs
ImgStore.xs
Log.xs
Makefile.PL
Network.xs
Notify.xs
Plugin.xs
PluginPref.xs
Pounce.xs
Prefs.xs
Privacy.xs
Proxy.xs
Prpl.xs
Purple.pm
Purple.xs
Request.xs
Roomlist.xs
SSLConn.xs
SavedStatuses.xs
Server.xs
Signal.xs
Smiley.xs
Sound.xs
Status.xs
Stringref.xs
Util.xs
XMLNode.xs
MANIFEST
typemap