Michael G Schwern wrote:
OK, manifypods is still in the doghouse. One thing that may be a problemOk, lemme see what I'm up to on integrating all this. Try the latest snapshot.
is the double dash at the end of the POD2MAN_EXE_macro definition. This
becomes a macro in the Makefile, and a minus sign at the end of a line
gets eaten. I'd have to look up what it means to the make utility, but
this example illustrates what it does:
$ type descrip.mms
bar = foo --
foo :
write sys$output "$(bar)"
$ mms/force
write sys$output "foo -"
foo -
I'm not sure what harm that's doing and don't fully understand what we
needed it for anyway, but I don't think you're getting what you expected.
The other thing is that $self->{MAN1PODS} and $self->{MAN3PODS} are
empty, so there is no input file. With no input file it defaults to
sending a bare template to the terminal, or at least that's what I think
is happening. Output below (possibly wrapped by MUA).
MCR perl_root:[000000]perl.exe "-ID0:[CRAIG.EXTUTILS-MAKEMAKER-SNAP.lib]" "-MExtUtils::Command::MM" -e "pod2man @ARGV" - --section=1
--perm_rw=
Manifying
..\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
..\"
..\" Standard preamble:
..\" ========================================================================
..de Sh \" Subsection heading
..br
..if t .Sp
..ne 5
..PP
\fB\\$1\fR
..PP
...
..de Sp \" Vertical space (when we can't use .PP)
..if t .sp .5v
..if n .sp
...
..de Vb \" Begin verbatim text
..ft CW
..nf
<snip>
