Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

O wise monks.

I am trying to retrofit a test suite on an existing application the directories of which have been laid out in a nonstandard way. I am unable to change the following conditions:

  1. Directory structure must stay as it is
  2. Have to use ExtUtils::MakeMaker

The difficulty that I am having is in advising make test to look for module files in a location other than blib/lib/

I am aware that I could put a use lib ... line at the top of every test and also that, alternatively I could specify a PM => {} mapping in the Makefile.PL to copy libraries to another location. Both of these solutions seem messy to me and possibly troublesome to maintain in the longer term.

Looking through the docs for ExtUtils::MakeMaker I am interested to note the PMLIBDIRS option that tells it (EUMM) where to look for nonstandard modules. However, when using this solution, make reproduces the whole path under blib/, again stopping make test from doing its thing.

I'm pretty sure I've explored the possibilities available to me but wonder if any of the whizz-kids know of a clean and simple solution to my troubles?

Any advice greatly appreciated,

Update: note that I am not asking how to tell Perl to look in a directory other than those usually found in @INC here,

MB

In reply to make test when modules in funny locations by matthewb

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2024-04-25 12:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found