This method, however, will also prevent a user from installing the software if the required libraries aren't installed

Or if the required libraries are installed in some place other than /usr/include.
Maybe that doesn't happen with wiringPi, but it's happened to me wrt other modules - and there's nothing that angers me more (wrt perl) than having to rewrite a Makefile.PL because of unrealistic author expectations regarding the location of the requisite library, or of the way in which it is being made available to the compilation.
If wiringPi.h does not get found during the compilation, then the cpantester report will record an "UNKNOWN" result, and little (if anything) would have been gained by detecting the missing dependency at the Makefile.PL step anyway.

It's at the compilation phase that the library files need to be found.
The Makefile.PL doesn't need the library. IMO it should just write the Makefile according to the EU::MM directives, and if the user hasn't made the required library available to the compilation, then (s)he will soon find out.

(Mind you, I'm perhaps a bit more "touchy" about this than most.)

Cheers,
Rob

In reply to Re^2: Running tests on module requiring installation of 3rd party utility by syphilis
in thread Running tests on module requiring installation of 3rd party utility by nysus

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.