Alien-Base-Wrapper
view release on metacpan or search on metacpan
designed to work with Alien::Base based aliens, but it should work with
any Alien which uses the same essential API.
In the first example (from the command line), this class acts as a
wrapper around the compiler and linker that Perl is configured to use.
It takes the normal compiler and linker flags and adds the flags
provided by the Aliens specified, and then executes the command. It
will print the command to the console so that you can see exactly what
is happening.
In the second example (from Makefile.PL non-dynamic), this class is
used to generate the appropriate ExtUtils::MakeMaker (EUMM) arguments
needed to WriteMakefile.
In the third example (from Makefile.PL dynamic), we do a quick check to
see if the simple linker flag -lfoo will work, if so we use that. If
not, we use a wrapper around the compiler and linker that will use the
alien flags that are known at build time. The problem that this form
attempts to solve is that compiler and linker flags typically need to
be determined at configure time, when a distribution is installed,
meaning if you are going to use an Alien module then it needs to be a
lib/Alien/Base/Wrapper.pm view on Meta::CPAN
This module acts as a wrapper around one or more L<Alien> modules. It is designed to work
with L<Alien::Base> based aliens, but it should work with any L<Alien> which uses the same
essential API.
In the first example (from the command line), this class acts as a wrapper around the
compiler and linker that Perl is configured to use. It takes the normal compiler and
linker flags and adds the flags provided by the Aliens specified, and then executes the
command. It will print the command to the console so that you can see exactly what is
happening.
In the second example (from Makefile.PL non-dynamic), this class is used to generate the
appropriate L<ExtUtils::MakeMaker> (EUMM) arguments needed to C<WriteMakefile>.
In the third example (from Makefile.PL dynamic), we do a quick check to see if the simple
linker flag C<-lfoo> will work, if so we use that. If not, we use a wrapper around the
compiler and linker that will use the alien flags that are known at build time. The
problem that this form attempts to solve is that compiler and linker flags typically
need to be determined at I<configure> time, when a distribution is installed, meaning
if you are going to use an L<Alien> module then it needs to be a configure prerequisite,
even if the library is already installed and easily detected on the operating system.
( run in 0.808 second using v1.01-cache-2.11-cpan-39bf76dae61 )