bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] New feature: direction arrow


From: Holger
Subject: Re: [Bug-gnubg] New feature: direction arrow
Date: Mon, 26 May 2003 12:45:17 +0200

At 07:53 25.05.2003 +0000, Joern Thyssen wrote:
On Sun, May 25, 2003 at 12:15:54AM +0200, Holger wrote
> On Sat, 24 May 2003 09:54:53 +0000, Joern Thyssen wrote:
> > On Fri, May 23, 2003 at 05:57:46PM +0200, Holger wrote
> > > Could someone please adjust the automake stuff accordingly?
> >
> > You need to make changes to configure.in and Makefile.am analogous to
> > the previous changes I just did a week ago (or so). Check the diff
> > between configure.in 1.91 and 1.92 and Makefile.am 1.95 and 1.96.
>
> Thanks for your hint. After a closer look it wasn't that frightening
> anymore as at first glance. ;)  Luckily, my changes weren't difficult.

Not difficult, but obviously wrong ;).

> I hope though, that I didn't forget anything. If you or someone else
> on *nix could check it please and generate and commit the dependent
> files, too?

Unless someone else does it, I'll do it Monday.

I've just tried to do it on Solaris. But it fails. It doesn't find AM_PATH_LIBART. Do I have to copy the contents of libart.m4 or should it find it by itself?

> Moreover, concerning Makefile.am I've some questions:
>
> Why are @FT2_CFLAGS@ and @GTKEXTRA_CFLAGS@ in COMMON_INCS and
> @FT2_LIBS@ and @GTKEXTRA_LIBS@ in COMMON_LIBS ?
> Shouldn't they be better under the 'if USE_GTK' branch in INCLUDES and
> gnubg_LDADD, respectively?

I can't remember that the FT2 does, but you're right about GTKEXTRA.

> Then I wonder about $(SOUND_INCS) $(PNG_LIBS) $(SOUND_SOURCES)
> $(FONT_SOURCES) $(SOUND_LIBS) $(PNG_LIBS) under the 'Plain' branch. I
> guess these shouldn't be necessary for the TTY version.

No, the tty version can export PNG pictures (html images and "export
position png") so it needs libpng and font-stuff. Also, the tty version
uses sounds so it needs the sound libraries.

Ah, I didn't realize this.

> Out of curiosity: After looking around some more I tripped over all
> those variable assignments in the beginning of doc/Makefile.in (and in
> ./lib/ and ./m4/). I can't explain myself how they get generated from
> doc/Makefile.am. I don't see anything there that could expand to such
> a list.

Which variables are you particular interested in?

None really. Just trying to understand how it works and where they come from.

Some of them are standard autoconf variables. Others are generated from
our macros (or macros used by our macros) in configure.in, e.g.,
ARTSC_CFLAGS og PKG_CONFIG etc.

Does any particular line in Makefile.am generate this list? Or is it some automatism that always produces this depending on what macros are found?
I relate e.g. to these lines in Makefile.in:
GNUPLOT = @GNUPLOT@
GTK_LIBS = @GTK_LIBS@

Regards,

Holger




reply via email to

[Prev in Thread] Current Thread [Next in Thread]