Getting started with Pidgin development
michael.p.thompson at gmail.com
Tue Nov 26 11:52:08 EST 2013
The separate local user thing is a good idea, I like that.
I am a Debian user and vim is where I do almost all of my development, so
that should work out well.
Thanks for the advice,
On Tue, Nov 26, 2013 at 8:48 AM, Mark Doliner <mark at kingant.net> wrote:
> On Sat, Nov 23, 2013 at 4:53 PM, Mike Thompson
> <michael.p.thompson at gmail.com> wrote:
> > I was curious about development setups and practices. I am able to
> > from the head of the repo. Is there any easy way to Sandbox pidgin? have
> > not look in user profile paths and the like? Is this a common development
> > practice?
> I usually pass --prefix=/home/mark/pidgin to autogen.sh or configure
> to have it install to a local directory. You could pass
> --config=/home/mark/alternate_dot_purple to use a different ~/.purple
> directory (though personally I just do my development as a separate
> local user because I find it to be easier and more isolated).
> > In a more general note, does anyone know of any articles or resources on
> > development paradigms that work well with Pidgin? or how do you go about
> > doing it? Another course of action here might be to do all of this
> inside a
> > VM. Any advice you have for getting going would be welcome.
> I think most of us tend to use simple text editors (vim, emacs, etc)
> and "make install" from a command line. A VM seems like overkill
> unless you're running on Windows but prefer to develop on Linux or you
> want to build against/test exotic versions of libraries (e.g. compile
> your own cutting edge glib or gstreamer or something).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel