Hi,
I am trying to choose between makemaker and build for use with my
SWIG-generated .so file. I would prefer to use Build, as it is the shiny thing
moving forward and would also dovetail more easily with what others in my
organization are doing.
However I haven't figured out how to cause Build to include a pre-compiled
library file. It's not XS, and I don't want to do the entire build of the .so
using the c_sources directive; the real build process happens elsewhere.
With MakeMaker, I can do this:
Makefile.PL:
#!/usr/bin/perl
use ExtUtils::MakeMaker;
WriteMakefile(
'NAME' => 'Mycompany::libfoo',
'VERSION_FROM' => 'lib/Mycompany/libfoo.pm',
'OBJECT' => 'lib/Mycompany/libfoo.so'
);
and the libfoo.so will be recognized and installed (along with the .bs file) as
expected.
I would prefer to use Build with --install_base however I cannot figure out how
to include the .so file in the Build.PL. M::B doesn't seem to have an
equivalent of makemaker's OBJECT attribute.
I am also bewildered by the radically different install paths used by makemaker
compared to what you get using Build with --install_base. Is there a standard
or a best practice defined somewhere?
I have read all the docs and mailing lists I can find; some of the folks using
XS come close to some of the same issues, but not quite (because Build DOES
include support for XS, specifically).
Any help is appreciated. Thx.
