Best way to keep a plugin outside of the pidgin source tree?

[Ibrahim Awwal]

Oh right, I'm an idiot. That should have been obvious, but I guess I'm 
not thinking today.

--Ibrahim Awwal

Casey Ho wrote:
> You can write a custom Makefile which places your code in a different 
> directory.  Some large plugins do this (autoprofile, IIRC).
>
> -Casey
>
> On Wed, Jun 10, 2009 at 12:19 PM, Ibrahim Awwal 
> <ibrahim.awwal at gmail.com <mailto:ibrahim.awwal at gmail.com>> wrote:
>
>     Hi,
>     I'm trying my hand at developing a plugin for Pidgin, and I was
>     wondering what the best way is to keep a plugin's source outside of
>     the Pidgin source tree? The main problem is that it's a bit annoying
>     to keep it in the plugins directory in the pidgin source if you want
>     to use version control. Right now I'm just using a symlink to my
>     plugin's source file in the plugins directory, but is there a better
>     way to do this? Thanks for the help
>     --Ibrahim Awwal
>
>     _______________________________________________
>     Devel mailing list
>     Devel at pidgin.im <mailto:Devel at pidgin.im>
>     http://pidgin.im/cgi-bin/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20090610/7073c490/attachment.html>