Re: [qub] install: how does this part work?

[Rusty B. <ru...@rl...>]

> stephan@jareth:~/cvs/qub/gamesets/lib/icons >cat Makefile.am
> xpmdir = $(pkgdatadir)/icons
>
> XPMS = $(wildcard *.xpm)
> xpm_DATA = $(XPMS)
> EXTRA_DIST = $(XPMS)
>
> Okay, i understand the EXTRA_DIST, but how the hell does the install
> process know that $xmpdir is the right dir to send EXTRA_DIST stuff to?
> Is "xpm_DATA" a way of saying "*.xpm goes to $pkgdatadir"?

Close--everything you list in xpm_DATA (or xpm_PROGRAMS, xpm_LIBRARIES,
etc.) gets installed in $(xpmdir).  (That's just the way automake works.)
To add a new installation directory, you go

foodir = $(path_to)/foo/stuff
foo_DATA = foodata1 foodata2 ...

If that's the only Makefile.am where you're going to be using $(foodir),
then it seems fine to define it there; otherwise, you can put it in
common.am (or AC_SUBST it in configure.in? I forget) so that any
Makefile.am can go "foo_DATA = ..."

> What i'm trying to do is to install a couple of gcoms built at install-time
> (using the new installation of gcommaker), and maybe copy a sample gameset
> over to ~/gameroot.

(I think you don't want to put anything in ~ during the install; better, I
think, to have qub copy it from $(pkgdatadir)/gameroot or something at
startup if ~/gameroot doesn't exist.  Doesn't it already do that with some
files or directories that it expects to find?)

--Rusty