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 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.
perl does have its own configure for modules, but I couldn't find any
documentation on how to do this for a perl program suite. Plus, the perl
configure way did not seem as flexible or as nice as ac/am.
> Ti> But I can't seem to make automake behave nicely. I'm using
> Ti> bin_SCRIPTS and libexec_SCRIPTS to do the make stuff, but I want a
> Ti> section called make "docs" to be run when someone just types
> Ti> 'make' (basically because make docs does a few pod2* commands).
>
> There are several ways to do this.
>
> If you plan to install the docs, just make them data:
>
> docdir = $(prefix)/install/directory/for/docs
> doc_DATA = list the outputs
>
> This will cause the docs to be built by whatever rules you include for
> building them.
Thanks! I'll try that. Could I do this with other types of data (i.e., conf
files, templates, etc)?
> Ti> make prep
>
> What does this do?
This would do some things that are needed to be done before install actually
happens. It's something related to the program's functionality and couldn't
explain it without explaining the program suite :)
> Tom
>
>
