Re: [MacPerl] Creating MacPerl Module Requirements

[Chris Nandor <pudge@pobox.com>]

At 15.51 -0700 2000.03.14, Joseph A. DiVerdi wrote:
>I am working on creating a Perl module for exclusive use with Macintosh
>hardware. Is it necessary or useful to create a Makefile.pl file in the
>distribution? If so, what purpose does it serve and what functionality does it
>provide?

Yes, the Makefile.PL is parsed when the distribution is dropped on 
installme, so installme knows what to do with it.

The basic Makefile.PL will look like this:

use ExtUtils::MakeMaker;
# See lib/ExtUtils/MakeMaker.pm for details of how to influence
# the contents of the Makefile that is written.
WriteMakefile(
     NAME			=> 'MP3::Info',
     VERSION_FROM	=> 'Info.pm', # finds $VERSION
);


It has the name of the module, and the file that contains $VERSION 
(which is also added to the list of files to install).

Something else important for your module is that Mac files, ones with 
resource forks that need to be maintained, need to be MacBinarized. 
The best way to package the distribution once the data is ready is to 
drop it on tarzipme, and then manually decide which files get to 
remain as text (plain font), regular unchanged binary (italic font), 
and which are MacBinary (bold font).  The module file with the XCMDs 
or XFCNs should be MacBinarized, with the bold font.

That's about it, I think.

-- 
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org