Re^3: let Makefile.PL to do the Readme file for me -- new target?

Rolf, no offense meant, but you seem to want this to be difficult; it's really not.

For example, did you notice the name of that module: it starts with "Win32"? The solution I showed functions perfectly in Strawberry Perl on Windows, out of the box.

Strawberry gives you the gcc build environment, with dmake (older strawberries) or gmake (newer strawberries) with perl -V:make showing the make variant to use. No extra work on your part. No bash emulation needed.

Using a perl module to build a makefile is part of the standard ExtUtils::MakeMaker environment.

Data::IEEE754::Tools Makefile.PL shows similar syntax, with the same syntax working on both Windows and Linux environments.

Using the Makefile.PL -> Makefile to add extra targets, to automate extra things for development, is an intended use of the ExtUtils::MakeMaker environment. If you don't like it, that's your perogative; you don't have to use it. But it is a system that works, even on Windows with Strawberry Perl.

Comment on Re^3: let Makefile.PL to do the Readme file for me -- new target? Download Code

Replies are listed 'Best First'.
Re^4: let Makefile.PL to do the Readme file for me -- new target? by LanX (Saint) on Jan 20, 2021 at 17:53 UTC
I have to apologize if you had the impression I was criticizing your code. Sorry. :/ It's a great peace of work showing a lot of nifty automization. I replied to you in this thread because you offered an elaborated example. What I meant was the whole concept, to use Perl to create two extra layers of different languages. It feels like embedding Sed to create Awk to me. Those levels of indirection must lead to problems. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery} edit s/atomization/automization/	[reply]
Re^5: let Makefile.PL to do the Readme file for me -- new target? by pryrt (Abbot) on Jan 20, 2021 at 18:11 UTC
Understood. It might be an extra level or two, but it's been working for ExtUtils::MakeMaker, even on Windows, at least as far back as 2002, and making use of the Makefile generated from a perl Makefile.PL is part of their design philosophy. I know other similar tools make use of a ./Build.PL, but I haven't used that toolset, so don't know if that idiom has an intermediate step as well, or not. Since I had some experience in automating README and similar tasks using MakeMaker for my few distros, I figured I'd share that knowledge.	[reply]
Re^6: let Makefile.PL to do the Readme file for me -- new target? by LanX (Saint) on Jan 20, 2021 at 18:25 UTC
Again, sorry! I said "we use" and was questioning the general approach, which is the mainstream as far as I understand. And I can also understand that most of the first Perl programmers came from a C background. I'm certainly not criticizing you and thankful for you sharing your approach. My concern was on a meta level ... I've heard people talking about Ruby's own native build process Rake and the benefits and synergies this creates. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^7: let Makefile.PL to do the Readme file for me -- new target? by bliako (Abbot) on Jan 20, 2021 at 19:13 UTC
Re^8: let Makefile.PL to do the Readme file for me -- new target? by LanX (Saint) on Jan 21, 2021 at 15:24 UTC
Some notes below your chosen depth have not been shown here
Re^8: let Makefile.PL to do the Readme file for me -- new target? by LanX (Saint) on Jan 20, 2021 at 19:26 UTC
Some notes below your chosen depth have not been shown here
Re^4: let Makefile.PL to do the Readme file for me -- new target? by LanX (Saint) on Jan 21, 2021 at 00:57 UTC
> Strawberry ... No extra work on your part. No bash emulation needed. Does it also work with ActiveState "without extra work" or do I need to install bash there? (in continuation of Re^2: dmake and bash on Win?) Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]

edit