Re: platform specific notes

[Gary V. Vaughan]

Hallo Ralf!

Ralf Wildenhues wrote:
>>All fine, except that you need to 'cd $(srcdir)' first in the make rule,
> 
> 
> I don't understand why this should be necessary; it breaks use of $<.
> I put it in the patch below, though.

Yes, but I'm not sure we're allowed to use $< in automake rules anyway
(incase the package builder has a degenerate make installed).

We have to build it in $srcdir so that make dist and make distcheck know
where to find it, and there is never any conflict between a notes.txt
from the dist tarball in $srcdir, and a spurious one rebuilt in $builddir.
It is possible to write rules that work like this, and use a $builddir
copy over a $srcdir copy of a file, but madness lies that way -- hence
some of the infinite loop problems we had in libtool make before Alexandre
reminded me of the Golden Rule :-)

> I had to change a couple more details -- setting SUFFIXES does not work
> with the hacked-up Makefile, so I went for a simple rule.

Thats probably better for automake anyhow.

> One more question: Do you think we should install notes.txt?

No, the info manual contains all the information, and is the right place
to document a GNU package.  Unless you wanted to add a libtoolize option
to copy it into a package's source tree... as LIBTOOL maybe?  That might
help to raise the profile of the notes section, and generate more bug
reports against it so we can keep it up to date. I have no strong feelings
about that either way.

Cheers,
        Gary.
-- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature