[Glade-users] Testing Glade 3 on Suse 9.1

[Tristan Van Berkom <tristan van berkom gmail com> (Tristan Van Berkom)]

On Sat, 20 Nov 2004 01:08:36 +0100, Ra=FAl Moratalla
<raul moratalla ono com> wrote:
> Hi, I would like to test Glade 3 on my system. I am using Suse 9.1 with t=
he
> latest version of gnome and gtk and I downloaded the source code of glade
> from cvs.

Thats great to hear ;-)

Right now glade-3 is in a wierd state because of the integration of libglad=
e
as a glade-file loader/saver, so most of the bleeding edge development is
in a branch (name: LIBGLADE_INTEGRATION), because we dont want to
push everyone to apply the libglade patch just to be able to work on glade-=
3.

The latest version of the libglade patch is available as an attatchment of=
=20
gnome bugzilla 156612 and will be integrated into libglade when it reaches
a minute level of maturity (and then we close the branch off).

So basicly what I'm saying is you'll get better results if you use the=20
branch right now ;-)

[...]
> I run autogen.sh but seems that as my system uses automake 1.9 there are =
some
> problems. Also there are some problems with macros:

[...]
> ***Error***: You must have automake >=3D 1.4 installed
>   to build glade.  Download the appropriate package for
>   from your distribution or get the source tarball at
>     http://ftp.gnu.org/pub/gnu/automake/automake-1.4.tar.gz

Looks like you already found your first bug ;-)

Maybe its something in configure ? || gnome autogen.sh ?

/me is curious ...

[...]
> ***Error***: some autoconf macros required to build glade
>   were not found in your aclocal path, or some forbidden
>   macros were found.  Perhaps you need to adjust your
>   ACLOCAL_PATH?
> =20
> Does anyone know how to solve this?

I think that aclocal doesn't check /usr/local/share/aclocal by default &
that gtk+ & alot of packages install in the /usr/local prefix by default.

I would run a quick `find /usr -name "*.m4"' to find all the directories ne=
eded
for your ACLOCAL_PATH and set that up (also to ensure that you have all
the ".m4" files).


Cheers,
                                              -Tristan