My understanding from similar recent investigations is that Module::Build is newer than the old Makefile.PL tools and should be used instead. But Dist::Zilla offers even better tools for the author (though is hard to install), and Module::Install is even better than Module::Build for whatever technical reasons and in working with up-to-date best practices. (see link)

It seems there is a lot to learn about testing, and module creation scripts are well behind the curve in what they set up for you.

The normal installation process will run the C compiler if necessary. For these build tools, you just have to use the proper naming and directory convention and it knows what to do.

In reply to Re: Perl & SWIG best practices? by John M. Dlugosz
in thread Perl & SWIG best practices? by Pic

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.