view libpurple/plugins/perl/common/Stringref.xs @ 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

#include "module.h"

MODULE = Purple::Stringref  PACKAGE = Purple::Stringref  PREFIX = purple_stringref_
PROTOTYPES: ENABLE

int
purple_stringref_cmp(s1, s2)
	Purple::Stringref s1
	Purple::Stringref s2

size_t
purple_stringref_len(stringref)
	Purple::Stringref stringref

Purple::Stringref
purple_stringref_new(class, value)
	const char *value
    C_ARGS:
	value

Purple::Stringref
purple_stringref_new_noref(class, value)
	const char *value
    C_ARGS:
	value

Purple::Stringref
purple_stringref_ref(stringref)
	Purple::Stringref stringref

void
purple_stringref_unref(stringref)
	Purple::Stringref stringref

const char *
purple_stringref_value(stringref)
	Purple::Stringref stringref