Re: Devel::CheckLib: Please break our code!

I would appreciate a documented layout of the said prereq file, so Makefile.PL/Build.PL would not necessarily need to use Devel::CheckLib. The idea is great though.

Also, I'm not sure if this is in the scope, but it would be great to have an option for a module to have a chance to re-run Makefile.PL after the missing dependencies were installed. Imagine one day someone releases something like bin::libjpeg.pm that installs libjpeg.so, and that can actually be used as an installable dependency.

Comment on Re: Devel::CheckLib: Please break our code!

Replies are listed 'Best First'.
Re^2: Devel::CheckLib: Please break our code! by DrHyde (Prior) on Oct 22, 2007 at 09:43 UTC
The bit that goes at the start of Makefile.PL (or Build.PL) looks something like this: `use lib qw(inc); use Devel::CheckLib; # Prompt the user here for any paths and other configuration check_lib_or_exit( # fill in what you prompted the user for here lib => [qw(cthulhu fhtagn)] );` [download] While you could, in theory, extract all the relevant code from the module and put it straight into your Makefile.PL, there's a lot of it. Building and linking C code in a cross-platform way is a pain in the arse.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Devel::CheckLib: Please break our code!
by DrHyde (Prior) on Oct 22, 2007 at 09:43 UTC

use lib qw(inc);
use Devel::CheckLib;

# Prompt the user here for any paths and other configuration

check_lib_or_exit(
    # fill in what you prompted the user for here
    lib => [qw(cthulhu fhtagn)]
);
[download]

[reply]
[d/l]