>> docdir = $(prefix)/install/directory/for/docs
>> doc_DATA = list the outputs
Ti> Thanks! I'll try that. Could I do this with other types of data
Ti> (i.e., conf files, templates, etc)?
Yeah, you can do it for just about anything.
This capability is documented, I think.
Tom
Peter> Alternatively, the GNU standards could catch up with reality
Peter> and make `docdir' a standard directory. Not everyone uses
Peter> Texinfo.
For GNU Standards changes you'd have to write to RMS.
Tom
Tom Tromey writes:
> If you plan to install the docs, just make them data:
>
> docdir = $(prefix)/install/directory/for/docs
> doc_DATA = list the outputs
Alternatively, the GNU standards could catch up with reality and make
`docdir' a standard directory. Not everyone uses Texinfo.
--
From: "Tom Tromey" <[EMAIL PROTECTED]>
To: "Ti Leggett" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 08, 2000 12:16 PM
Subject: Re: Support for making perl scripts...
> Ti> I really have two questions. First, is there an easy way
Ti> I really have two questions. First, is there an easy way to extend
Ti> automake/autoconf to support perl package installations.
It probably isn't hard to do.
But I thought Perl had its own build and install program.
Ti> But I can't seem to make automake behave nicely. I'm using
Ti> bin_SCRIP
I really have two questions. First, is there an easy way to extend
automake/autoconf to support perl package installations. I have a suite of
programs I've helped to write in perl and I want to package them up. The
package includes normal perl scripts and perl modules. I think I've figured
out how
