Differences between current version and predecessor to the previous major change of perlmodinstall(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Monday, June 3, 2002 6:50:48 pm | by perry | |
| Older page: | version 1 | Last edited on Monday, June 3, 2002 6:50:48 pm | by perry | Revert |
@@ -133,17 +133,17 @@
That's all you need to do on Unix systems with dynamic linking. Most Unix systems have dynamic linking--if yours doesn't, or if for another reason you have a statically-linked perl, ''and'' the module requires compilation, you'll need to build a new Perl binary that includes the module. Again, you'll probably need to be root.
__If you're running Windows 95 or NT with
-the ActiveState port of Perl__
+the !
ActiveState port of Perl__
A. DECOMPRESS
You can use the shareware __Winzip__ program ( http://www.winzip.com ) to decompress and unpack modules.
B. UNPACK
-If you used WinZip, this was already done for you.
+If you used !
WinZip, this was already done for you.
C. BUILD
Does the module require compilation (i.e. does it have files that end in .xs, .c, .h, .y, .cc, .cxx, or .C)? If it does, you're on your own. You can try compiling it yourself if you have a C compiler. If you're successful, consider uploading the resulting binary to CPAN for others to use. If it doesn't, go to INSTALL .
@@ -163,14 +163,14 @@
A. DECOMPRESS
When you download the module, make sure it ends in either ''.tar.gz'' or ''.zip''. Windows browsers sometimes download .tar.gz files as _tar.tar, because early versions of Windows prohibited more than one dot in a filename.
-You can use the shareware __WinZip__ program (
+You can use the shareware __!
WinZip__ program (
http://www.winzip.com ) to decompress and unpack
modules.
-Or, you can use InfoZip's unzip utility (
+Or, you can use !
InfoZip's unzip utility (
http://www.cdrom.com/pub/infozip/ ) to uncompress
.zip files; type unzip yourmodule.zip in
your shell.
@@ -223,42 +223,42 @@
__untarzipme__ droplet, which will decompress and unpack
for you.
-__Or__, you can either use the shareware __StuffIt
+__Or__, you can either use the shareware __!
StuffIt
Expander__ program ( http://www.aladdinsys.com/expander/ )
-in combination with __DropStuff with Expander Enhancer__
+in combination with __!
DropStuff with Expander Enhancer__
( http://www.aladdinsys.com/dropstuff/ ) or the freeware
-__MacGzip__ program (
+__!
MacGzip__ program (
http://persephone.cps.unizar.es/general/gente/spd/gzip/gzip.html
).
B. UNPACK
-If you're using untarzipme or StuffIt, the archive should be
+If you're using untarzipme or !
StuffIt, the archive should be
extracted now. __Or__, you can use the freeware
__suntar__ or ''Tar'' (
-http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/
+http://hyperarchive.lcs.mit.edu/!
HyperArchive/Archive/cmp/
).
C. BUILD
Check the contents of the distribution. Read the module's
documentation, looking for reasons why you might have
-trouble using it with MacPerl. Look for ''.xs'' and
+trouble using it with !
MacPerl. Look for ''.xs'' and
''.c'' files, which normally denote that the distribution
must be compiled, and you cannot install it ``out of the
box.'' (See `` PORTABILITY ''.)
-If a module does not work on MacPerl but should, or needs to
+If a module does not work on !
MacPerl but should, or needs to
be compiled, see if the module exists already as a port on
-the MacPerl Module Porters site (http://pudge.net/mmp/). For
-more information on doing XS with MacPerl
+the !
MacPerl Module Porters site (http://pudge.net/mmp/). For
+more information on doing XS with !
MacPerl
yourself, see Arved Sandstrom's XS tutorial
(http://macperl.com/depts/Tutorials/), and then consider
uploading your binary to the CPAN and
registering it on the MMP site.
@@ -293,11 +293,11 @@
Then move the files (probably just the ''.pm'' files,
though there may be some additional ones, too; check the
module documentation) to their final destination: This will
most likely be in $ENV{MACPERL}site_lib: (i.e.,
-HD:MacPerl folder:site_lib:). You can add new paths
+HD:!
MacPerl folder:site_lib:). You can add new paths
to the default @INC in the Preferences menu item in
-the MacPerl application ($ENV{MACPERL}site_lib: is
+the !
MacPerl application ($ENV{MACPERL}site_lib: is
added automagically). Create whatever directory structures
are required (i.e., for Some::Module, create
$ENV{MACPERL}site_lib:Some: and put
Module.pm in that directory).
@@ -307,9 +307,9 @@
it):
#!perl -w
-use AutoSplit;
+use !
AutoSplit;
my $dir =
__If you're on the DJGPP port of
@@ -400,9 +400,9 @@
C. BUILD
Make sure you have MMS (from Digital) or the
-freeware MMK ( available from MadGoat at
+freeware MMK ( available from !
MadGoat at
http://www.madgoat.com ). Then type this to create the
DESCRIP .MMS for the module:
