Front page | perl.perl5.porters |
Postings from September 2011
<URL: https://rt.cpan.org/Ticket/Display.html?id=69318 > Weird, RT didn't mail me your last reply. Anyhow: Note ahead: I know almost nothing about C. It's been almost a decade since i last wrote a C program. > I think the general way to accomplish that is to just try to compile a > small program. Isn't that what Configure does? No idea. Completely outside of my expertise. > I wonder if delegating to ExtUtils::CBuilder would be sufficient. I'd > love to see all that nasty Liblist code go away. Again, I have no idea and do not know the module. Though, casual looking reveals: "However, it is not intended as a general cross-platform interface to all your C building needs." > Alternatively... do we need to go through that process at all? Good question! Why indeed. I personally have no clue why that is necessary. I can only guess at it being meant to make it possible for authors to indicate multiple libraries with EUMM choosing the one that actually exists. But that's a wild guess. > Christian, I think of anyone you know Liblist the most. Or if nothing > else you're brave enough to mess with it. What do you think? I can, by virtue of perl -d, understand what it does. Sadly this does not mean i know why it does that. Even the initial commit in the git repo on the 16th january of 2002 only says: > ExtUtils::Liblist - determine libraries to use and how to use them > > This utility takes a list of libraries in the form C<-llib1 -llib2 > -llib3> and returns lines suitable for inclusion in an extension > Makefile. But does not qualify why it does so. What I'm thinking right now is that first of all we need to find the why of the matter. Only then can an informed decision be made.Thread Previous | Thread Next