On Fri, Apr 16, 2010 at 8:53 PM, Russ Allbery <[email protected]> wrote:
> Ole Tange <[email protected]> writes:
>
>> I have the feeling the configuration files would be extremely simple:
>
>> 'make' should run 'pod2man program' to generate the man page
>> 'make install' should copy the program to .../bin, and the man page to
>> .../man1
>
> dist_bin_SCRIPTS = program
> man_MANS = program.1
>
> program.1: program
> pod2man --release='$(PACKAGE_VERSION)' --center='$(PACKAGE_NAME)' \
> --section=1 program > program.1
>
> CLEANFILES = program.1
Thanks, Russ. I believe this is half the answer. But it seems I still
need a couple of lines. Here is what I have now:
$ cat src/Makefile.am
dist_bin_SCRIPTS = parallel
man_MANS = parallel.1
parallel.1: parallel
pod2man --release='$(PACKAGE_VERSION)' --center='$(PACKAGE_NAME)' \
--section=1 parallel > parallel.1
CLEANFILES = parallel.1
$ cat Makefile.am
SUBDIRS = src
$ cat configure.ac
AC_INIT([parallel], [1.0], [[email protected]])
AM_INIT_AUTOMAKE([-Wall -Werror foreign])
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_FILES([
Makefile
src/Makefile
])
AC_OUTPUT
When running:
autoreconf --install -W gnu; ./configure ; make
the manpage is not made. Doing
cd src
make parallel.1
does not make the man page either.
The good part is that 'make install' would have done the right thing
had the man page been made.
I probably just need a single line to get make to make the man page. Hints?
/Ole
