Alien-Build

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

  - Fix bug in Test::Alien xs_ok would crash with multiple alines with xs_load methods.

0.98_01   2017-08-16 17:50:17 -0400
  - Added Alien::Build::Plugin::Build::CMake (which was briefly in its own distribution).

0.97      2017-08-16 17:36:36 -0400
  - Production release identical to 0.96_01

0.96_01   2017-08-16 11:30:50 -0400
  - Added Alien::Build::Plugin::Build::Make (which was briefly in its own distribution).
  - Removing accidental dependency on Archive::Tar
    (it should be optional, though it is available as part of the Perl core on 5.10+)
  - Fixed bug where Test::Alien xs_ok could throw an exception instead
    of failing gracefully.
  - Test::Alien alien_ok does not crash when undef is passed to it
  - C++ support in Test::Alien xs_ok is deprecated and will be removed on or after
    31 August 2017.  This feature was experimental.  This capability will be developed
    in the separate distribution Test-Alien-CPP
  - remove Test::Alien::CanCompileCpp.  This module will come bundled with
    Test-Alien-CPP instead.

Changes.Alien-Base  view on Meta::CPAN

  - added alien_bin_requires property to Alien::Base::ModuleBuild (plicease gh#84, gh#88)
  - added alien_msys property to Alien::Base::ModuleBuild (plicease gh#86)

0.005_03  Sep 23, 2014
  - Inline tests requires Inline 0.56 (skip elsewise)
  - Document Inline 0.56 or better required for Inline integration

0.005_02  Sep 23, 2014
  - silence Archive::Extract deprecation warning
    (we explicitly specify it as a prereq)
  - remove accidental undeclared dependency on YAML introduced in 0.005_01
  - fixed test failures introduced in 0.005_01

0.005_01  Sep 22, 2014
  - fixes with static library detection when pkg-config is not available (plicease gh#79, gh#75)
  - support for Inline 'with' (plicease gh#71, gh#77, gh#78)
  - fix prereqs for Text::ParseWords and PkgConfig (plicease gh#73, gh#70)

0.005  Sep 11, 2014
  - improved documentation coverage

lib/Alien/Build.pm  view on Meta::CPAN

  $self->install_prop->{extract} ||= $ret;
  $ret ? $ret : ();
}


sub build
{
  my($self) = @_;

  # save the evironment, in case some plugins decide
  # to alter it.  Or us!  See just a few lines below.
  local %ENV = %ENV;

  my $stage = _path($self->install_prop->{stage});
  $stage->mkpath;

  my $tmp;

  if($self->install_type eq 'share')
  {

lib/Alien/Build/Manual/FAQ.pod  view on Meta::CPAN

require this Alien in the C<share> block (as you should), then these prereqs
will only be pulled in during a share install when they are needed.

Please see the L<Alien::Autotools> documentation for specifics on how it
can be used in your L<alienfile>.

=item patch the package locally before build

You can use the L<alienfile/patch> directive to patch the alienized package
locally before building.  This can sometimes be challenging because Autotools
uses timestamps in order to decide what needs to be rebuilt, and patching
can sometimes confuse it into thinking more needs to be rebuilt than what
actually does.

=item build configure and tarball

You can also build the configure script during development of your alien,
generate the tarball and provide it somewhere like GitHub and use that
as the source instead of the original source.  This should usually be
a last resort if the other two methods prove too difficult.

lib/Alien/Build/Manual/image/PluginAuthor-flowchart.svg  view on Meta::CPAN

<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:lucid="lucid" width="2520" height="3275.09"><g transform="translate(0 0)" lucid:page-tab-id="0_0"><path d="M0 0h3456v3952H0z" fill="#fff"/><path d="M440.93 2504a...

lib/Test/Alien.pm  view on Meta::CPAN

 my $run = interpolate_run_ok $command, $message;

This is the same as L</run_ok> except it runs the command through the interpolator first.

=head1 ENVIRONMENT

=over 4

=item C<TEST_ALIEN_ALWAYS_KEEP>

If this is defined then it will override the built in logic that decides if
the temporary files generated by L</xs_ok> should be kept when the test file
terminates.  If set to true the generated files will always be kept.  If
set to false, then they will always be removed.

=item C<TEST_ALIEN_ALIENS_MISSING>

By default, this module will warn you if some tools are used without first
invoking L</alien_ok>.  This is usually a mistake, but if you really do
want to use one of these tools with no aliens loaded, you can set this
environment variable to false.