That won't alter %Config::Config at all, but as long as the values are taken from this local %Config then you can perhaps make use of it.

I've been through the EU code, for the most part it refers to it's local %Config, though there are the following:

In Base.pm: $Config::Config{perlpath})
In Install.pm: $Config::Config{make}
In MakeMaker.pm: $Config::Config{eunicefix}
In MM_Os2.pm: $Config::Config{lib_ext}
In Mkbootstrap.pm: @Config::Config{qw(osname dlsrc)}
In Mksymlists.pm: $Config::Config{archname}
In Mksymlists.pm: $Config::Config{version}
In Mksymlists.pm: $Config::Config{'cc'}
In Mksymlists.pm: $Config::Config{d_vms_case_sensitive_symbols}

Love the consistency ...

So as I see it as long as you don't want to muck with the above listed values one should be good to go using ExtUtils::MakeMaker::Config in ones Makefile.PL.
Obliviously this is only going to work within the scope of the current Makefile.PL.

However, my preference would still be to overwrite %Config::Config itself as that is cleaner and simpler (IMO).

I agree, However it appears big brother does not ...

I still find this does not serve my needs.
For my needs the real issue is, on *nix, ExtUtils::Liblist::Kid will not allow fully qualified library names.

The standard technique for including a Static library over a Shared library is to use the fully qualified filename without the '-l' library tag. As in:
-L/usr/local/lib /usr/local/lib/libmylib.a
This tells the make tool chain to blindly use it, where '-lmylib' says search for libmylib.so (or versions of it) if found use it, if not look for libmylib.a (or versions of it).

ExtUtils::Liblist::Kid ignores and tosses out anything that doesn't have either a '-L' or '-l' tag.

My words for ExtUtils-MakeMaker: If you don't understand it, pass it on ... Don't toss it!
Someone may be smarter then you and know what to do with it!

And I don't mean a human ... I mean the make tool chain.

Peace out.

In reply to Re^4: MakeMaker and Library filename extensions by Anonymous Monk
in thread MakeMaker and Library filename extensions by Anonymous Monk

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.