On November 24, 2005, Ralf wrote:
> > My original two cases were:
> >
> > 1. ACLOCAL_AMFLAGS = -I ../../scripts/m4
>
> which pointed outside your package and thus is a nono (do
> not specify relative paths which point to something outside
> of your package).
>
> > or
> >
> > 2. ACLOCAL_AMFLAGS
Hi David,
* David Byron wrote on Thu, Nov 24, 2005 at 03:55:37AM CET:
> On November 17, 2005, Ralf wrote:
> >
> > Regarding the issue whether to put them all into aclocal.m4
> > or into separate files below m4/: Recent aclocal versions
> > will generate a bunch of
> >
> > m4_include([m4/foo.m4]
On November 17, 2005, Ralf wrote:
> * David Byron wrote on Wed, Nov 16, 2005 at 04:37:45PM CET:
> > On November 15, 2005, Ralf wrote:
> >
> > > First idea: In the directory, where aclocal searches by
> > > default ($prefix/share/aclocal, usually), edit/create the
> > > file `dirlist' to point to
* David Byron wrote on Wed, Nov 16, 2005 at 04:37:45PM CET:
> On November 15, 2005, Ralf wrote:
>
> > First idea: In the directory, where aclocal searches by
> > default ($prefix/share/aclocal, usually), edit/create the
> > file `dirlist' to point to the directory your macros are in.
> > Then, #2
On November 15, 2005, Ralf wrote:
> First idea: In the directory, where aclocal searches by
> default ($prefix/share/aclocal, usually), edit/create the
> file `dirlist' to point to the directory your macros are in.
> Then, #2 will work without any ACLOCAL_AMFLAGS.
I could see this working, but th
Hi David,
* David Byron wrote on Wed, Nov 16, 2005 at 12:40:42AM CET:
> I've defined some macros that I'd like to share across projects. Seems
> to me I've got two choices for getting them in my dist tarball:
>
> 1. include the macros I wrote in the files I wrote
> 2. include the macros I wrote
