diff options
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlwin32.pod')
| -rw-r--r-- | Master/tlpkg/tlperl/lib/pods/perlwin32.pod | 283 |
1 files changed, 92 insertions, 191 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlwin32.pod b/Master/tlpkg/tlperl/lib/pods/perlwin32.pod index f9c3353b6d7..67869cac6cc 100644 --- a/Master/tlpkg/tlperl/lib/pods/perlwin32.pod +++ b/Master/tlpkg/tlperl/lib/pods/perlwin32.pod @@ -8,8 +8,7 @@ perlwin32 - Perl under Windows =head1 SYNOPSIS -These are instructions for building Perl under Windows 9x/NT/2000/XP -on the Intel x86 and Itanium architectures. +These are instructions for building Perl under Windows 2000 and later. =head1 DESCRIPTION @@ -26,56 +25,62 @@ only relevant to people building Perl on Unix-like systems. In particular, you can safely ignore any information that talks about "Configure". -You may also want to look at two other options for building -a perl that will work on Windows NT: the README.cygwin and -README.os2 files, each of which give a different set of rules to -build a Perl that will work on Win32 platforms. Those two methods -will probably enable you to build a more Unix-compatible perl, but -you will also need to download and use various other build-time and -run-time support software described in those files. +You may also want to look at one other option for building a perl that +will work on Windows: the README.cygwin file, which give a different +set of rules to build a perl for Windows. This method will probably +enable you to build a more Unix-compatible perl, but you will also +need to download and use various other build-time and run-time support +software described in that file. This set of instructions is meant to describe a so-called "native" -port of Perl to Win32 platforms. This includes both 32-bit and +port of Perl to the Windows platform. This includes both 32-bit and 64-bit Windows operating systems. The resulting Perl requires no additional software to run (other than what came with your operating system). Currently, this port is capable of using one of the following compilers on the Intel x86 architecture: - Borland C++ version 5.02 or later - Microsoft Visual C++ version 2.0 or later - MinGW with gcc gcc version 2.95.2 or later - Gcc by mingw.org gcc version 2.95.2 or later + Borland C++ version 5.02 or later + Microsoft Visual C++ version 6.0 or later + Gcc by mingw.org gcc version 3.2 or later Gcc by mingw-w64.sf.net gcc version 4.4.3 or later Note that the last two of these are actually competing projects both delivering complete gcc toolchain for MS Windows: -- http://mingw.org - delivers gcc toolchain targeting 32-bit Windows - platform. - Use version 3.2.x or later for the best results with this compiler. -- http://mingw-w64.sf.net - delivers gcc toolchain targeting both 64-bit - Windows and 32-bit Windows platforms (despite the project name "mingw-w64" - they are not only 64-bit oriented). They deliver the native gcc compilers - + cross-compilers that are also supported by perl's makefile. + +=over 4 + +=item L<http://mingw.org> + +Delivers gcc toolchain targeting 32-bit Windows platform. + +=item L<http://mingw-w64.sf.net> + +Delivers gcc toolchain targeting both 64-bit Windows and 32-bit Windows +platforms (despite the project name "mingw-w64" they are not only 64-bit +oriented). They deliver the native gcc compilers and cross-compilers +that are also supported by perl's makefile. + +=back The Borland C++ and Microsoft Visual C++ compilers are also now being given away free. The Borland compiler is available as "Borland C++ Compiler Free Command Line Tools" and is the same compiler that ships with the full "Borland C++ Builder" product. The Microsoft compiler is available as -"Visual C++ Toolkit 2003" or "Visual C++ 2005/2008 Express Edition" (and also -as part of the ".NET Framework SDK") and is the same compiler that ships with -"Visual C++ .NET 2003 Professional" or "Visual C++ 2005/2008 Professional" -respectively. +"Visual C++ Toolkit 2003" or "Visual C++ 2005/2008/2010 Express Edition" (and +also as part of the ".NET Framework SDK") and is the same compiler that ships +with "Visual C++ .NET 2003 Professional" or "Visual C++ 2005/2008/2010 +Professional" respectively. This port can also be built on IA64/AMD64 using: Microsoft Platform SDK Nov 2001 (64-bit compiler and tools) MinGW64 compiler (gcc version 4.4.3 or later) -The MS Platform SDK can be downloaded from http://www.microsoft.com/. -The MinGW64 compiler is available at http://sourceforge.net/projects/mingw-w64. +The Windows SDK can be downloaded from L<http://www.microsoft.com/>. +The MinGW64 compiler is available at L<http://sourceforge.net/projects/mingw-w64>. The latter is actually a cross-compiler targeting Win64. There's also a trimmed down compiler (no java, or gfortran) suitable for building perl available at: -http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2.zip +L<http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2.zip> NOTE: If you're using a 32-bit compiler to build perl on a 64-bit Windows operating system, then you should set the WIN64 environment variable to "undef". @@ -85,24 +90,24 @@ Also, the trimmed down compiler only passes tests when USE_ITHREADS *= define This port fully supports MakeMaker (the set of modules that is used to build extensions to perl). Therefore, you should be able to build and install most extensions found in the CPAN sites. -See L<Usage Hints for Perl on Win32> below for general hints about this. +See L<Usage Hints for Perl on Windows> below for general hints about this. -=head2 Setting Up Perl on Win32 +=head2 Setting Up Perl on Windows =over 4 =item Make You need a "make" program to build the sources. If you are using -Visual C++ or the Platform SDK tools under Windows NT/2000/XP, nmake -will work. All other builds need dmake. +Visual C++ or the Windows SDK tools, nmake will work. Builds using +the Borland compiler or gcc need dmake. dmake is a freely available make that has very nice macro features and parallelability. A port of dmake for Windows is available from: - http://search.cpan.org/dist/dmake/ +L<http://search.cpan.org/dist/dmake/> Fetch and install dmake somewhere on your path. @@ -118,17 +123,11 @@ available in the win32 subdirectory of the Perl source distribution. =item Command Shell -Use the default "cmd" shell that comes with NT. Some versions of the +Use the default "cmd" shell that comes with Windows. Some versions of the popular 4DOS/NT shell have incompatibilities that may cause you trouble. If the build fails under that shell, try building again with the cmd shell. -The nmake Makefile also has known incompatibilities with the -"command.com" shell that comes with Windows 9x. You will need to -use dmake and makefile.mk to build under Windows 9x. - -The surest way to build it is on Windows NT/2000/XP, using the cmd shell. - Make sure the path to the build directory does not contain spaces. The build usually works in this circumstance, but some tests will fail. @@ -144,7 +143,7 @@ See L</"Make"> 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 or C:\Program Files\Microsoft Visual Studio\VC98\Bin. +like 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, @@ -154,31 +153,26 @@ and edit win32/config.vc to change "make=nmake" into "make=dmake". The latter step is only essential if you want to use dmake as your default make for building extensions using MakeMaker. -=item Microsoft Visual C++ 2008 Express Edition +=item Microsoft Visual C++ 2008/2010 Express Edition -This free version of Visual C++ 2008 Professional contains the same compiler -and linker that ship with the full version, and also contains everything -necessary to build Perl, rather than requiring a separate download of the -Platform SDK like previous versions did. +These free versions of Visual C++ 2008/2010 Professional contain the same +compilers and linkers that ship with the full versions, and also contain +everything necessary to build Perl, rather than requiring a separate download +of the Windows SDK like previous versions did. -This package can be downloaded by searching for "Visual Studio 2008 Express -Edition" in the Download Center at -http://www.microsoft.com/downloads/search.aspx?displaylang=en. (Providing exact +These packages can be downloaded by searching in the Download Center at +L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact links to these packages has proven a pointless task because the links keep on changing so often.) -Install Visual C++ 2008, then setup your environment using +Install Visual C++ 2008/2010 Express, then setup your environment using, e.g. - C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat + C:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools\vsvars32.bat (assuming the default installation location was chosen). Perl should now build using the win32/Makefile. You will need to edit that -file to set - - CCTYPE = MSVC90FREE - -first. +file to set CCTYPE to MSVC90FREE or MSVC100FREE first. =item Microsoft Visual C++ 2005 Express Edition @@ -186,23 +180,19 @@ This free version of Visual C++ 2005 Professional contains the same compiler and linker that ship with the full version, but doesn't contain everything necessary to build Perl. -You will also need to download the "Platform SDK" (the "Core SDK" and "MDAC +You will also need to download the "Windows SDK" (the "Core SDK" and "MDAC SDK" components are required) for more header files and libraries. These packages can both be downloaded by searching in the Download Center at -http://www.microsoft.com/downloads/search.aspx?displaylang=en. (Providing exact +L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact links to these packages has proven a pointless task because the links keep on changing so often.) -Try to obtain the latest version of the Platform SDK. Sometimes these packages +Try to obtain the latest version of the Windows SDK. Sometimes these packages contain a particular Windows OS version in their name, but actually work on other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK" also runs on Windows XP SP2 and Windows 2000. -According to the download pages these packages are only supported on Windows -2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows -NT probably won't work. - Install Visual C++ 2005 first, then the Platform SDK. Setup your environment as follows (assuming default installation locations were chosen): @@ -242,19 +232,15 @@ Framework Redistributable" to be installed first. This can be downloaded and installed separately, but is included in the "Visual C++ Toolkit 2003" anyway. These packages can all be downloaded by searching in the Download Center at -http://www.microsoft.com/downloads/search.aspx?displaylang=en. (Providing exact +L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact links to these packages has proven a pointless task because the links keep on changing so often.) -Try to obtain the latest version of the Platform SDK. Sometimes these packages +Try to obtain the latest version of the Windows SDK. Sometimes these packages contain a particular Windows OS version in their name, but actually work on other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK" also runs on Windows XP SP2 and Windows 2000. -According to the download pages these packages are only supported on Windows -2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows -NT probably won't work. - Install the Toolkit first, then the Platform SDK, then the .NET Framework SDK. Setup your environment as follows (assuming default installation locations were chosen): @@ -341,55 +327,13 @@ shells available after you install the Platform SDK from the Start Menu. =item MinGW release 3 with gcc -The latest release of MinGW at the time of writing is 3.1.0, which contains -gcc-3.2.3. It can be downloaded here: - - http://www.mingw.org/ +Perl can be compiled with gcc from MinGW release 3 and later (using gcc 3.2.x +and later). It can be downloaded here: -Perl also compiles with earlier releases of gcc (2.95.2 and up). See below -for notes about using earlier versions of MinGW/gcc. - -And perl also compiles with gcc-4.3.0 and up, and perhaps even some of the -earlier 4.x.x versions. +L<http://www.mingw.org/> You also need dmake. See L</"Make"> above on how to get it. -=item MinGW release 1 with gcc - -The MinGW-1.1 bundle contains gcc-2.95.3. - -Make sure you install the binaries that work with MSVCRT.DLL as indicated -in the README for the GCC bundle. You may need to set up a few environment -variables (usually ran from a batch file). - -There are a couple of problems with the version of gcc-2.95.2-msvcrt.exe -released 7 November 1999: - -=over - -=item * - -It left out a fix for certain command line quotes. To fix this, be sure -to download and install the file fixes/quote-fix-msvcrt.exe from the above -ftp location. - -=item * - -The definition of the fpos_t type in stdio.h may be wrong. If your -stdio.h has this problem, you will see an exception when running the -test t/lib/io_xs.t. To fix this, change the typedef for fpos_t from -"long" to "long long" in the file i386-mingw32msvc/include/stdio.h, -and rebuild. - -=back - -A potentially simpler to install (but probably soon-to-be-outdated) bundle -of the above package with the mentioned fixes already applied is available -here: - - http://downloads.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip - ftp://ftp.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip - =back =head2 Building @@ -400,7 +344,7 @@ here: 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 +versions of nmake that come with Visual C++ or the Windows SDK, and a dmake "makefile.mk" that will work for all supported compilers. The defaults in the dmake makefile are setup to build using MinGW/gcc. @@ -437,19 +381,6 @@ You may also need to comment out the C<DELAYLOAD = ...> line in the Makefile if you're using VC++ 6.0 without the latest service pack and the linker reports an internal error. -If you are using VC++ 4.2 or earlier then you'll have to change the /EHsc -option in the CXX_FLAG macro to the equivalent /GX option. - -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 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 -fail at run time. - If you want build some core extensions statically into perl's dll, specify them in the STATIC_EXT macro. @@ -460,19 +391,18 @@ Be sure to read the instructions near the top of the makefiles carefully. Type "dmake" (or "nmake" if you are using that make). This should build everything. Specifically, it will create perl.exe, -perl512.dll at the perl toplevel, and various other extension dll's +perl514.dll at the perl toplevel, and various other extension dll's under the lib\auto directory. If the build fails for any reason, make sure you have done the previous steps correctly. =back -=head2 Testing Perl on Win32 +=head2 Testing Perl on Windows Type "dmake test" (or "nmake test"). This will run most of the tests from the testsuite (many tests will be skipped). -There should be no test failures when running under Windows NT/2000/XP. -Many tests I<will> fail under Windows 9x due to the inferior command shell. +There should be no test failures. Some test failures may occur if you use a command shell other than the native "cmd.exe", or if you are building from a path that contains @@ -485,7 +415,7 @@ If you're using the Borland compiler, you may see a failure in op/taint.t arising from the inability to find the Borland Runtime DLLs on the system default path. You will need to copy the DLLs reported by the messages from where Borland chose to install it, into the Windows system directory -(usually somewhere like C:\WINNT\SYSTEM32) and rerun the test. +(usually somewhere like C:\WINDOWS\SYSTEM32) and rerun the test. If you're using Borland compiler versions 5.2 and below, you may run into problems finding the correct header files when building extensions. For @@ -507,7 +437,7 @@ avoid these errors. Please report any other failures as described under L<BUGS AND CAVEATS>. -=head2 Installation of Perl on Win32 +=head2 Installation of Perl on Windows Type "dmake install" (or "nmake install"). This will put the newly built perl and the libraries under whatever C<INST_TOP> points to in the @@ -527,7 +457,7 @@ 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 +=head2 Usage Hints for Perl on Windows =over 4 @@ -561,7 +491,7 @@ following entries (of type REG_SZ or REG_EXPAND_SZ) may be set: Note the C<$]> in the above is not literal. Substitute whatever version of perl you want to honor that entry, e.g. C<5.6.0>. Paths must be -separated with semicolons, as usual on win32. +separated with semicolons, as usual on Windows. =item File Globbing @@ -581,12 +511,11 @@ with what Windows offers by way of a command shell. The crucial thing to understand about the Windows environment is that the command line you type in is processed twice before Perl sees it. -First, your command shell (usually CMD.EXE on Windows NT, and -COMMAND.COM on Windows 9x) preprocesses the command line, to handle -redirection, environment variable expansion, and location of the -executable to run. Then, the perl executable splits the remaining -command line into individual arguments, using the C runtime library -upon which Perl was built. +First, your command shell (usually CMD.EXE) preprocesses the command +line, to handle redirection, environment variable expansion, and +location of the executable to run. Then, the perl executable splits +the remaining command line into individual arguments, using the +C runtime library upon which Perl was built. It is particularly important to note that neither the shell nor the C runtime do any wildcard expansions of command-line arguments (so @@ -596,7 +525,7 @@ using a non-standard shell, be inconsistent). The only (useful) quote character is the double quote ("). It can be used to protect spaces and other special characters in arguments. -The Windows NT documentation has almost no description of how the +The Windows documentation has almost no description of how the quoting rules are implemented, but here are some general observations based on experiments: The C runtime breaks arguments at spaces and passes them to programs in argc/argv. Double quotes can be used to @@ -655,7 +584,7 @@ Discovering the usefulness of the "command.com" shell on Windows 9x is left as an exercise to the reader :) One particularly pernicious problem with the 4NT command shell for -Windows NT is that it (nearly) always treats a % character as indicating +Windows is that it (nearly) always treats a % character as indicating that environment variable expansion is needed. Under this shell, it is therefore important to always double any % characters which you want Perl to see (for example, for hash variables), even when they are @@ -665,11 +594,11 @@ quoted. The Comprehensive Perl Archive Network (CPAN) offers a wealth of extensions, some of which require a C compiler to build. -Look in http://www.cpan.org/ for more information on CPAN. +Look in L<http://www.cpan.org/> for more information on CPAN. Note that not all of the extensions available from CPAN may work -in the Win32 environment; you should check the information at -http://testers.cpan.org/ before investing too much effort into +in the Windows environment; you should check the information at +L<http://testers.cpan.org/> before investing too much effort into porting modules that don't readily build. Most extensions (whether they require a C compiler or not) can @@ -690,12 +619,12 @@ ensure Config.pm knows about it. If you don't have nmake, you can either get dmake from the location mentioned earlier or get an old version of nmake reportedly available from: - http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/nmake15.exe +L<http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/nmake15.exe> Another option is to use the make written in Perl, available from CPAN. - http://www.cpan.org/modules/by-module/Make/ +L<http://www.cpan.org/modules/by-module/Make/> You may also use dmake. See L</"Make"> above on how to get it. @@ -774,27 +703,6 @@ binary will always expand unquoted command lines, which may not be what you want if you use a shell that does that for you. The expansion done is also somewhat less powerful than the approach suggested above. -=item Win32 Specific Extensions - -A number of extensions specific to the Win32 platform are available -from CPAN. You may find that many of these extensions are meant to -be used under the Activeware port of Perl, which used to be the only -native port for the Win32 platform. Since the Activeware port does not -have adequate support for Perl's extension building tools, these -extensions typically do not support those tools either and, therefore, -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 several other Win32 extensions from -CPAN in source form, along with many added bugfixes, and with MakeMaker -support. The latest version of this bundle is available at: - - http://search.cpan.org/dist/libwin32/ - -See the README in that distribution for building and installation -instructions. - =item Notes on 64-bit Windows Windows .NET Server supports the LLP64 data model on the Intel Itanium @@ -842,23 +750,22 @@ Embedding Perl inside a 64-bit application. Perl scripts on UNIX use the "#!" (a.k.a "shebang") line to indicate to the OS that it should execute the file using perl. -Win32 has no comparable means to indicate arbitrary files are +Windows has no comparable means to indicate arbitrary files are executables. Instead, all available methods to execute plain text files on -Win32 rely on the file "extension". There are three methods +Windows rely on the file "extension". There are three methods to use this to execute perl scripts: =over 8 =item 1 -There is a facility called "file extension associations" that will -work in Windows NT 4.0. This can be manipulated via the two -commands "assoc" and "ftype" that come standard with Windows NT -4.0. Type "ftype /?" for a complete example of how to set this -up for perl scripts (Say what? You thought Windows NT wasn't -perl-ready? :). +There is a facility called "file extension associations". This can be +manipulated via the two commands "assoc" and "ftype" that come +standard with Windows. Type "ftype /?" for a complete example of how +to set this up for perl scripts (Say what? You thought Windows +wasn't perl-ready? :). =item 2 @@ -894,7 +801,7 @@ avoids both problems is possible. A script called "runperl.bat" is available that can be copied to any filename (along with the .bat suffix). For example, if you call it "foo.bat", it will run the file "foo" when it is -executed. Since you can run batch files on Win32 platforms simply +executed. Since you can run batch files on Windows platforms simply by typing the name (without the extension), this effectively runs the file "foo", when you type either "foo" or "foo.bat". With this method, "foo.bat" can even be in a different location @@ -916,7 +823,7 @@ system. C<perldoc> is also a useful tool for browsing information contained in the documentation, especially in conjunction with a pager -like C<less> (recent versions of which have Win32 support). You may +like C<less> (recent versions of which have Windows support). You may have to set the PAGER environment variable to use a specific pager. "perldoc -f foo" will print information about the perl operator "foo". @@ -926,7 +833,7 @@ is assuming that Perl's normal behavior of opening a command-line window will go away. This isn't the case. If you want to start a copy of C<perl> without opening a command-line window, use the C<wperl> executable built during the installation process. Usage is exactly -the same as normal C<perl> on Win32, except that options like C<-h> +the same as normal C<perl> on Windows, except that options like C<-h> don't work (since they need a command-line window to print to). If you find bugs in perl, you can run C<perlbug> to create a @@ -957,21 +864,15 @@ that will be portable to other environments, see L<perlport> for a reasonably definitive list of these differences. Not all extensions available from CPAN may build or work properly -in the Win32 environment. See L</"Building Extensions">. +in the Windows environment. See L</"Building Extensions">. Most C<socket()> related calls are supported, but they may not behave as on Unix platforms. See L<perlport> for the full list. -Perl requires Winsock2 to be installed on the system. If you're -running Win95, you can download Winsock upgrade from here: - -http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp - -Later OS versions already include Winsock2 support. Signal handling may not behave as on Unix platforms (where it doesn't exactly "behave", either :). For instance, calling C<die()> or C<exit()> from signal handlers will cause an exception, since most -implementations of C<signal()> on Win32 are severely crippled. +implementations of C<signal()> on Windows are severely crippled. Thus, signals may work only for simple things like setting a flag variable in the handler. Using signals under this port should currently be considered unsupported. @@ -997,7 +898,7 @@ of O'Reilly and Associates, Inc. Used with permission. =item Jan Dubois E<lt>jand@activestate.comE<gt> -=item Steve Hay E<lt>steve.hay@uk.radan.comE<gt> +=item Steve Hay E<lt>steve.m.hay@googlemail.comE<gt> =back @@ -1026,6 +927,6 @@ Win9x support was added in 5.6 (Benjamin Stuhl). Support for 64-bit Windows added in 5.8 (ActiveState Corp). -Last updated: 29 August 2007 +Last updated: 18 November 2010 =cut |