[Module-build-general] Re: FW: Why is Module::Build looking for the module in lib directory?

[Ken W. <ke...@ma...>]

On Tuesday, June 17, 2003, at 05:54  PM, Mr. Lindsay Morris wrote:

> Ken, not sure you're on pa...@pe..., so I'm sending you this directly.
> I know you're busy - there's probably an obvious answer,
> so if you have time, I'd appreciate any hints.

Hi Lindsay,

You're right, I'm not on pa...@pe....

> ===========================================================
> lmorris - /tmp/SGlic >cat Build.PL
> use Module::Build;
> my $build = new Module::Build
> (
>         module_name => 'SGlic',
>         license => 'perl',
>         requires => {
>                 perl           => '5.6.1',
>                 Crypt::CapnMidNite   => '1.00',
>                 Filter::Util::Call  => 1.00,
>         },
> );
> $build->create_build_script;
>
> lmorris - /tmp/SGlic >fgrep VERSION SGlic.pm
> our $VERSION = '1.02';
>
> lmorris - /tmp/SGlic >perl Build.PL
> Checking whether your kit is complete...
> Looks good
> Can't open 'lib/SGlic.pm' for version: No such file or directory at
> /usr/lib/perl5/site_perl/5.8.0/Module/Build/Base.pm line 274.
> ===========================================================

It's telling the truth. =)  You should create a lib/ directory and put 
the SGlic.pm file in there.

This is one of the layouts that works with MakeMaker.  It's the default 
layout in Module::Build.  Alternate layouts need to be specified 
explicitly, because the aggressive behavior of MakeMaker in finding & 
installing modules wherever it can has been deemed undesirable in M::B.

  -Ken