view libpurple/plugins/mono/api/Debug.cs @ 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

using System;
using System.Runtime.CompilerServices;

namespace Purple
{
	public class Debug
	{
		public static int ALL = 0;
		public static int MISC = 1;
		public static int INFO = 2;
		public static int WARNING = 3;
		public static int ERROR = 4;
		public static int FATAL = 5;
		
		[MethodImplAttribute(MethodImplOptions.InternalCall)]
		extern private static void _debug(int type, string cat, string str);
		
		public static void debug(int type, string cat, string format)
		{
			_debug(type, cat, format);
		}
		
		public static void debug(int type, string cat, string format, params object[] args)
		{
			_debug(type, cat, String.Format(format, args));
		}
	}
}