User-side module building with ExtUtils::MakeMaker

[merkys]

Hello, I am interested in autogenerating Perl modules for my distribution during user-side builds. To be precise, I have a Parse::Yapp-driven module, which I want to build on the user's side (motivation: 1. the parser is too huge to include it in the source distribution, 2. SPOT/DRY). To build the module on the user-side, I add the following to WriteMakefile of Makefile.PL (using ExtUtils::MakeMaker):

depend => { pm_to_blib => 'blib/lib/OPTiMaDe/Filter/Parser.pm' },

and, at the end of the Makefile.PL:

sub MY::postamble {
<<'EOT'
blib/lib/OPTiMaDe/Filter/%.pm: %.yp
        mkdir --parents $(@D)
        yapp -v -m OPTiMaDe::Filter::Parser -o $@ $<
EOT
}

However, CPAN Testers run into a variety of troubles, from inability to find the rules to make the dependency, to 'yapp' not being found, and mkdir not working (mainly Windows). My question: is there a standard way to write plugins for ExtUtils::MakeMaker (Dist::Zilla or any other equivalent) to produce Perl modules on the client side?

[pryrt]

instead of hardcoding the mkdir command, which isn't known on all systems, use the $(MKPATH) from ExtUtils::MakeMaker's Makefile, which calls mkpath. As a side benefit, mkpath automatically generates necessary parents as well, so you don't need the --parents argument.

sub MY::postamble {
<<'EOT'
blib/lib/OPTiMaDe/Filter/%.pm: %.yp
        $(MKPATH) (@D)
        yapp -v -m OPTiMaDe::Filter::Parser -o $@ $<
EOT
}

[thomas895]

Perhaps you can include the generated parser, like how it's done in Verilog::Parser? There's still the original sources included for those who would like to hack on it; in that case you need flex/bison.

In particular, to address the question of the makefile, look here for inspiration

[Anonymous Monk]

if you insist on making users generate Use PL_FILES

Which make? Nmake? Dmake? Gmake? Mingw32-make?... Avoid postamble

also there is no source code too big to include

also including the source is equally SPOT/DRY

[Aldebaran]

also including the source is equally SPOT/DRY

I did a super search and a google search of what SPOT/DRY betoken and didn't find anything.

[Fletch]

Don't Repeat Yourself for that one; from context then maybe Single Point Of Truth ?

[Anonymous Monk]

https://en.wikipedia.org/wiki/SPOT#Technology
->https://en.wikipedia.org/wiki/Single_Point_of_Truth

->->https://en.wikipedia.org/wiki/Don%27t_repeat_yourself

DRY is misunderstood in a lot of online discussions, the true meaning is what SPOT describes

So for the OP, Parser.yp is the cannical reference, OPTiMaDe::Filter::Parser is the generated module that says this file is generated from the cannical reference Parser.yp , make all edits in Parser.yp

Distributing a OPTiMaDe::Filter::Parser.pm does not violate SPOT/DRY