From: Steve Hay Date: Fri, 30 Jul 2004 14:31:08 +0000 (+0000) Subject: A few minor updates to README.win32 (aka perlwin32) X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=00808b83cb115b43fc0c0ea4cde0afb36c1b9112;p=p5sagit%2Fp5-mst-13.2.git A few minor updates to README.win32 (aka perlwin32) p4raw-id: //depot/perl@23172 --- diff --git a/README.win32 b/README.win32 index b9ab612..3688a32 100644 --- a/README.win32 +++ b/README.win32 @@ -122,7 +122,8 @@ See L above. The nmake that comes with Visual C++ will suffice for building. You will need to run the VCVARS32.BAT file, usually found somewhere -like C:\MSDEV4.2\BIN. This will set your build environment. +like C:\MSDEV4.2\BIN or C:\Program Files\Microsoft Visual Studio\VC98\Bin. +This will set your build environment. You can also use dmake to build using Visual C++; provided, however, you set OSRELEASE to "microsft" (or whatever the directory name @@ -197,8 +198,7 @@ Make sure you are in the "win32" subdirectory under the perl toplevel. This directory contains a "Makefile" that will work with versions of nmake that come with Visual C++ or the Platform SDK, and a dmake "makefile.mk" that will work for all supported compilers. The -defaults in the dmake makefile are setup to build using Microsoft Visual -C++ 6.0 or newer. +defaults in the dmake makefile are setup to build using MinGW/gcc. =item * @@ -224,7 +224,7 @@ If you have either the source or a library that contains des_fcrypt(), enable the appropriate option in the makefile. A ready-to-use version of fcrypt.c, based on the version originally written by Eric Young at ftp://ftp.funet.fi/pub/crypt/mirrors/dsi/libdes/, is bundled with the -distribution. Set CRYPT_SRC to fcrypt.c to use this version. +distribution and CRYPT_SRC is set to use it. Alternatively, if you have built a library that contains des_fcrypt(), you can set CRYPT_LIB to point to the library name. Perl will also build without des_fcrypt(), but the crypt() builtin will @@ -289,19 +289,20 @@ Please report any other failures as described under L. Type "dmake install" (or "nmake install"). This will put the newly built perl and the libraries under whatever C points to in the Makefile. It will also install the pod documentation under -C<$INST_TOP\$VERSION\lib\pod> and HTML versions of the same under -C<$INST_TOP\$VERSION\lib\pod\html>. To use the Perl you just installed, -you will need to add two components to your PATH environment variable, -C<$INST_TOP\$VERSION\bin> and C<$INST_TOP\$VERSION\bin\$ARCHNAME>. -For example: +C<$INST_TOP\$INST_VER\lib\pod> and HTML versions of the same under +C<$INST_TOP\$INST_VER\lib\pod\html>. - set PATH c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH% +To use the Perl you just installed you will need to add a new entry to +your PATH environment variable: C<$INST_TOP\bin>, e.g. -If you opt to comment out INST_VER and INST_ARCH in the makefiles, the -installation structure is much simpler. In that case, it will be -sufficient to add a single entry to the path, for instance: + set PATH=c:\perl\bin;%PATH% - set PATH c:\perl\bin;%PATH% +If you opted to uncomment C and C in the makefile +then the installation structure is a little more complicated and you will +need to add two new PATH components instead: C<$INST_TOP\$INST_VER\bin> and +C<$INST_TOP\$INST_VER\bin\$ARCHNAME>, e.g. + + set PATH=c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH% =head2 Usage Hints for Perl on Win32 @@ -382,7 +383,7 @@ enclosing the whole argument within double quotes. The backslash and the pair of double quotes surrounding the argument will be stripped by the C runtime. -The file redirection characters "<", ">", and "|" can be quoted by +The file redirection characters "E", "E", and "|" can be quoted by double quotes (although there are suggestions that this may not always be true). Single quotes are not treated as quotes by the shell or the C runtime, they don't get stripped by the shell (just to make @@ -562,11 +563,11 @@ cannot be built using the generic steps shown in the previous section. To ensure smooth transitioning of existing code that uses the ActiveState port, there is a bundle of Win32 extensions that contains -all of the ActiveState extensions and most other Win32 extensions from +all of the ActiveState extensions and several other Win32 extensions from CPAN in source form, along with many added bugfixes, and with MakeMaker support. This bundle is available at: - http://www.cpan.org/authors/id/GSAR/libwin32-0.18.zip + http://www.cpan.org/modules/by-module/Win32/libwin32-0.191.zip See the README in that distribution for building and installation instructions. Look for later versions that may be available at the @@ -591,6 +592,8 @@ binaries transparently. This means that you could use a 32-bit build of Perl on a 64-bit system. Given this, why would one want to build a 64-bit build of Perl? Here are some reasons why you would bother: +=over + =item * A 64-bit native application will run much more efficiently on @@ -611,6 +614,8 @@ Embedding Perl inside a 64-bit application. =back +=back + =head2 Running Perl Scripts Perl scripts on UNIX use the "#!" (a.k.a "shebang") line to @@ -679,7 +684,9 @@ Here's a diversion: copy "runperl.bat" to "runperl", and type "runperl". Explain the observed behavior, or lack thereof. :) Hint: .gnidnats llits er'uoy fi ,"lrepnur" eteled :tniH -=item Miscellaneous Things +=back + +=head2 Miscellaneous Things A full set of HTML documentation is installed, so you should be able to use it if you have a web browser installed on your @@ -704,8 +711,6 @@ If you find bugs in perl, you can run C to create a bug report (you may have to send it manually if C cannot find a mailer on your system). -=back - =head1 BUGS AND CAVEATS Norton AntiVirus interferes with the build process, particularly if @@ -726,7 +731,7 @@ Some of the built-in functions do not act exactly as documented in L, and a few are not implemented at all. To avoid surprises, particularly if you have had prior exposure to Perl in other operating environments or if you intend to write code -that will be portable to other environments. See L +that will be portable to other environments, see L for a reasonably definitive list of these differences. Not all extensions available from CPAN may build or work properly @@ -744,8 +749,8 @@ variable in the handler. Using signals under this port should currently be considered unsupported. Please send detailed descriptions of any problems and solutions that -you may find to >, along with the output produced -by C. +you may find to EFE, along with the output +produced by C. =head1 ACKNOWLEDGEMENTS @@ -789,6 +794,6 @@ Win9x support was added in 5.6 (Benjamin Stuhl). Support for 64-bit Windows added in 5.8 (ActiveState Corp). -Last updated: 20 April 2002 +Last updated: 30 July 2004 =cut