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

[Felipe Contreras]

On Thu, Jun 11, 2009 at 12:19 AM, Ibrahim Awwal<ibrahim.awwal at gmail.com> wrote:
>
>
> Felipe Contreras wrote:
>
> On Wed, Jun 10, 2009 at 10:19 PM, Ibrahim Awwal<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
>
>
> You can see msn-pecan as an example:
> http://github.com/felipec/msn-pecan
>
>
>
> Thanks! It appears that msn-pecan uses one makefile for all platforms,
> rather than having a separate Makefile.mingw for Windows. Unfortunately, at
> least for me it also appears to not work since windows doesn't have
> pkg-config although cygwin does but it's not configured properly, but this
> should still be useful.

You can use pkg-config on windows, I haven't done that myself but it's
definitely doable.

What I do is use a mingw32 cross-compiler to compile for win32 on
Linux platform.

-- 
Felipe Contreras