|No such thing as a small change|
Re^4: MakeMaker and Library filename extensionsby Anonymous Monk
|on Jan 21, 2013 at 22:27 UTC||Need Help??|
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:
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.
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.
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:
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!
And I don't mean a human ... I mean the make tool chain.