develooper Front page | perl.perl5.porters | Postings from February 2009

Re: merging make_ext and make_ext_cross

Thread Previous | Thread Next
Craig A. Berry
February 8, 2009 17:36
Re: merging make_ext and make_ext_cross
Message ID:
On Sat, Feb 7, 2009 at 4:32 PM, Nicholas Clark <> wrote:
> On Sat, Feb 07, 2009 at 04:17:14PM -0600, Craig A. Berry wrote:
>> I have
>> no idea why we have always passed INST_LIB and INST_ARCHLIB nor whey
>> everybody else passes INSTALLDIR and INSTALLMAN3DIRS as pass-through
>> arguments, but I decided to start off with a bug-for-bug compatible
>> implementation and worry about the rest later.
> INSTALLMAN3DIRS I know - it avoids needing to specify it in each Makefile.PL
> It prevents the makefile trying to make man pages, which no longer works now
> that the podulators require POSIX, whilst the extensions are built with
> miniperl. It was added here:
> Except that it's not much use if just one platform is doing it, as Makefile.PLs
> ext-wide can't be simplified. I wasn't actually aware that the change had been
> made until I started on
> INSTALLDIR comes from this change:
> "Part of the MakeMaker 5.21 update."
> It's just that file, and I can't actually find any other reference to
> MakeMaker 5.21. The effect will be to cause the module to install in the
> "perl" library tree, rather than the sitelib tree.

Thanks.  As far as I know we never build man pages by default on VMS,
so we probably don't need those.

> Presumably setting INST_LIB and INST_ARCHLIB has the same
> effect? (But only on code, not man pages)

That seems right.  They've been there ever since's
predecessor came along back here:

All the changes I can think of to use in the VMS build and
handle flattened extension directories (where Foo::Bar might live
under ext/Foo-Bar) are now committed and pushed, so let THE PLAN

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About