Re: Help packaging the latest pidgin.

2008/1/30, Neil Munro <[email protected]>:
> On 30/01/2008, Isak Savo <[email protected]> wrote:
> >
> > There are two ways to use binreloc.
> > 1) The "normal" way: This involves changing the code to not rely on
> > hard coded paths. Basically find all locations in the code where it
> > has hard coded strings for e.g. datafiles and replace them with their
> > corresponding binreloc API function call.

> Ok, I'll try the tried and true method first, how do I go about doing it, I
> remember from your website that it's in the main Makefile.am that I try and
> change hard coded paths, but on a project like Pidgin I imagine I have to
> edit more than the main Makefile.am however, your website said if the
> package is also built for windows binreloc should not be required and Pidgin
> is packaged for windows, so I am not entirely sure what to do. Or even where
> to begin.

It's actually not so much Makefile.am, but rather the actual source code files.

I recommend you read the tutorial, which walks through your exact situation:
   http://autopackage.org/docs/tutorials/glb.html

It goes through all the steps you need to learn. And one of these
steps is about binreloc.

Then there's the binreloc documentation:
   http://autopackage.org/docs/binreloc/
and the API reference (you should use the glib api, since pidgin is a
gtk project):
   http://autopackage.org/docs/binreloc/doxygen/glib-binreloc.html

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]