Re: Compiling Jim Picks snapshots
- From: Raja R Harinath <harinath cs umn edu>
- To: Phil Dawes <philipd parallax co uk>
- Cc: gnome-list gnome org
- Subject: Re: Compiling Jim Picks snapshots
- Date: 14 May 1998 11:07:26 -0500
Phil Dawes <philipd@parallax.co.uk> writes:
> The only way I could get the various gnome modules to compile from Jim
> Picks CVS snapshots (ftp://ftp.jimpick.com/pub/gnome/snap) was to:
>
> 1) unpack the gnome-* snapshot
> 2) unpack the Gnome-common snapshot
> 3) copy all the autoconf input file type gubbins (macros folder, intl,
> etc..) from gnome-common into the gnome-* snapshot.
Right.
> 4) do aclocal, automake, autoconf (or something like that) (the
> autogen.sh scripts didn't work)
That's right too. But, why isn't `autogen.sh' working? Can you send me
a log.
> 5) configure, make etc.. as usual.
>
> I've noticed that the redhat snapshots only require steps 4 and 5, and
> the autogen.sh script does this for you. Am I doing something wrong, or
> is this the best way of building gnome from Jim Picks stapshots?
Nope. This is the way to build from the current snapshots. Of course,
the `autogen.sh' should have worked.
> How does the CVS repository do this? - are the things from gnome-common
> implicitly copied when you check out the archive?
Yes. This is achieved by adding a line per module in the
CVSROOT/modules file.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]