samtregar has asked for the wisdom of the Perl Monks concerning the following question:

Greetings Monks. I'm working on the installation system I sketched out here some time ago. With some critical help from perrin, things are working really well.

My problem is that it's pretty slow, and I think a lot of that has to do with building man-pages I don't need. To explain, during the build phase around 75 Perl modules are built and installed using the usual 'perl Makefile.PL && make install' steps. LIB is set to where I want the compiled modules installed, and PREFIX is set to a junk box so I can throw out any binaries, man-pages or other refuse I don't need after the install is done.

I think I could make the build step at least twice as fast if I could convince ExtUtils::MakeMaker to not bother building man-pages from POD source. Does anyone know how to do that? A trip through the docs and source didn't give me anything obvious.

-sam

  • Comment on Can MakeMaker be convinced not to build man pages?

Replies are listed 'Best First'.
Re: Can MakeMaker be convinced not to build man pages?
by tantarbobus (Hermit) on Mar 19, 2004 at 19:07 UTC

    Is this what you are looking for? 

    $make_options{MAN1PODS} = {};
$make_options{MAN3PODS} = {};

ExtUtils::MakeMaker::WriteMakefile(%make_options);

    [download]
[reply]
[d/l]
      Hmmm, that's a hint anyway. Any way to set that from outside Makefile.PL? I'd rather not get into trying to automatically modify other people's Perl code if I can help it. Some module's Makefile.PL's are pretty complicated (see Imager for a fine example).

      Thanks,
      -sam

[reply]

        This appears to work (assuming a bash shell): 

        perl Makefile.PL  MAN1PODS=\{\} MAN3PODS=\{\}

        [download]
[reply]
[d/l]

Back to Seekers of Perl Wisdom