Its an open bug?Thanks for that. One of those links led me to XML::Parser and how it deals with the problem. And then I remembered that some of Tassilo von Parseval's modules parse the command line for INC and LIBS args, so I took a look at his Unix::Statgrab Makefile.PL.
Seems to work fine if the top level Makefile.PL does:
our %args = map { split /\s*=\s*/ } @ARGV;
our $LIBS_LOC = $args{ LIBS } || "-lgmp";
our $INC_LOC = $args{ INC };
and then the subdir Makefile.PL simply has to specify:
WriteMakfile(
....
LIBS => $LIBS_LOC,
INC => $INC_LOC,
....
);
I haven't yet looked at any caveats with that approach. I'll get to that now.
Thanks again.
Cheers,
Rob
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.