Commit | Line | Data |
---|---|---|
9baed986 LC |
1 | If you read this file _as_is_, just ignore the funny characters you |
2 | see. It is written in the POD format (see pod/perlpod.pod) which is | |
3 | specially designed to be readable as is. | |
4 | ||
5 | =head1 NAME | |
6 | ||
7 | perlwin32 - Perl under Windows | |
8 | ||
9 | =head1 SYNOPSIS | |
10 | ||
b906aaa5 | 11 | These are instructions for building Perl under Windows 2000 and later. |
9baed986 LC |
12 | |
13 | =head1 DESCRIPTION | |
14 | ||
15 | Before you start, you should glance through the README file | |
16 | found in the top-level directory to which the Perl distribution | |
17 | was extracted. Make sure you read and understand the terms under | |
18 | which this software is being distributed. | |
19 | ||
20 | Also make sure you read L<BUGS AND CAVEATS> below for the | |
21 | known limitations of this port. | |
22 | ||
23 | The INSTALL file in the perl top-level has much information that is | |
24 | only relevant to people building Perl on Unix-like systems. In | |
25 | particular, you can safely ignore any information that talks about | |
26 | "Configure". | |
27 | ||
b906aaa5 JD |
28 | You may also want to look at one other option for building a perl that |
29 | will work on Windows: the README.cygwin file, which give a different | |
30 | set of rules to build a perl for Windows. This method will probably | |
31 | enable you to build a more Unix-compatible perl, but you will also | |
32 | need to download and use various other build-time and run-time support | |
33 | software described in that file. | |
9baed986 LC |
34 | |
35 | This set of instructions is meant to describe a so-called "native" | |
b906aaa5 | 36 | port of Perl to the Windows platform. This includes both 32-bit and |
9baed986 LC |
37 | 64-bit Windows operating systems. The resulting Perl requires no |
38 | additional software to run (other than what came with your operating | |
39 | system). Currently, this port is capable of using one of the | |
40 | following compilers on the Intel x86 architecture: | |
41 | ||
b906aaa5 | 42 | Borland C++ version 5.02 or later |
ffc8a9ad | 43 | Microsoft Visual C++ version 6.0 or later (*) |
ceb0c681 | 44 | Gcc by mingw.org gcc version 3.2 or later |
fa58a56f S |
45 | Gcc by mingw-w64.sf.net gcc version 4.4.3 or later |
46 | ||
ffc8a9ad SH |
47 | (*) NOTE: Support for Visual C++ 2010 is not yet complete. This latest |
48 | version of VC++ introduces some new C<errno.h> constants which conflict | |
49 | with Perl's current setting of them to match the corresponding WSAE* | |
50 | constants' values. Until this issue is resolved you will see several test | |
51 | failures (in F<cpan/autodie/t/flock.t>, F<dist/IO/t/io_multihomed.t >, | |
52 | F<dist/Net-Ping/t/450_service.t> and F<dist/Net-Ping/t/510_ping_udp.t>) | |
53 | and experience other problems in code involving sockets. | |
54 | ||
fa58a56f S |
55 | Note that the last two of these are actually competing projects both |
56 | delivering complete gcc toolchain for MS Windows: | |
b906aaa5 | 57 | |
42d76a89 MS |
58 | =over 4 |
59 | ||
60 | =item L<http://mingw.org> | |
61 | ||
62 | Delivers gcc toolchain targeting 32-bit Windows platform. | |
b906aaa5 | 63 | |
42d76a89 MS |
64 | =item L<http://mingw-w64.sf.net> |
65 | ||
66 | Delivers gcc toolchain targeting both 64-bit Windows and 32-bit Windows | |
67 | platforms (despite the project name "mingw-w64" they are not only 64-bit | |
68 | oriented). They deliver the native gcc compilers and cross-compilers | |
69 | that are also supported by perl's makefile. | |
70 | ||
71 | =back | |
9baed986 | 72 | |
758e4bce SH |
73 | The Borland C++ and Microsoft Visual C++ compilers are also now being given |
74 | away free. The Borland compiler is available as "Borland C++ Compiler Free | |
75 | Command Line Tools" and is the same compiler that ships with the full | |
76 | "Borland C++ Builder" product. The Microsoft compiler is available as | |
2a46176f SH |
77 | "Visual C++ Toolkit 2003" or "Visual C++ 2005/2008/2010 Express Edition" (and |
78 | also as part of the ".NET Framework SDK") and is the same compiler that ships | |
79 | with "Visual C++ .NET 2003 Professional" or "Visual C++ 2005/2008/2010 | |
80 | Professional" respectively. | |
7241fd28 | 81 | |
fa58a56f | 82 | This port can also be built on IA64/AMD64 using: |
9baed986 LC |
83 | |
84 | Microsoft Platform SDK Nov 2001 (64-bit compiler and tools) | |
fa58a56f | 85 | MinGW64 compiler (gcc version 4.4.3 or later) |
9baed986 | 86 | |
42d76a89 MS |
87 | The Windows SDK can be downloaded from L<http://www.microsoft.com/>. |
88 | The MinGW64 compiler is available at L<http://sourceforge.net/projects/mingw-w64>. | |
fa58a56f S |
89 | The latter is actually a cross-compiler targeting Win64. There's also a trimmed |
90 | down compiler (no java, or gfortran) suitable for building perl available at: | |
42d76a89 | 91 | L<http://strawberryperl.com/package/kmx/64_gcctoolchain/mingw64-w64-20100123-kmx-v2.zip> |
fa58a56f S |
92 | |
93 | NOTE: If you're using a 32-bit compiler to build perl on a 64-bit Windows | |
94 | operating system, then you should set the WIN64 environment variable to "undef". | |
d774b2d8 CJ |
95 | Also, the trimmed down compiler only passes tests when USE_ITHREADS *= define |
96 | (as opposed to undef) and when the CFG *= Debug line is commented out. | |
9baed986 LC |
97 | |
98 | This port fully supports MakeMaker (the set of modules that | |
99 | is used to build extensions to perl). Therefore, you should be | |
100 | able to build and install most extensions found in the CPAN sites. | |
b906aaa5 | 101 | See L<Usage Hints for Perl on Windows> below for general hints about this. |
9baed986 | 102 | |
b906aaa5 | 103 | =head2 Setting Up Perl on Windows |
9baed986 LC |
104 | |
105 | =over 4 | |
106 | ||
107 | =item Make | |
108 | ||
109 | You need a "make" program to build the sources. If you are using | |
b906aaa5 JD |
110 | Visual C++ or the Windows SDK tools, nmake will work. Builds using |
111 | the Borland compiler or gcc need dmake. | |
9baed986 LC |
112 | |
113 | dmake is a freely available make that has very nice macro features | |
114 | and parallelability. | |
115 | ||
116 | A port of dmake for Windows is available from: | |
117 | ||
42d76a89 | 118 | L<http://search.cpan.org/dist/dmake/> |
9baed986 | 119 | |
13e18e90 | 120 | Fetch and install dmake somewhere on your path. |
9baed986 LC |
121 | |
122 | There exists a minor coexistence problem with dmake and Borland C++ | |
123 | compilers. Namely, if a distribution has C files named with mixed | |
124 | case letters, they will be compiled into appropriate .obj-files named | |
125 | with all lowercase letters, and every time dmake is invoked | |
126 | to bring files up to date, it will try to recompile such files again. | |
127 | For example, Tk distribution has a lot of such files, resulting in | |
128 | needless recompiles every time dmake is invoked. To avoid this, you | |
129 | may use the script "sync_ext.pl" after a successful build. It is | |
130 | available in the win32 subdirectory of the Perl source distribution. | |
131 | ||
132 | =item Command Shell | |
133 | ||
8cbe99e5 | 134 | Use the default "cmd" shell that comes with Windows. Some versions of the |
9baed986 LC |
135 | popular 4DOS/NT shell have incompatibilities that may cause you trouble. |
136 | If the build fails under that shell, try building again with the cmd | |
137 | shell. | |
138 | ||
9baed986 LC |
139 | Make sure the path to the build directory does not contain spaces. The |
140 | build usually works in this circumstance, but some tests will fail. | |
141 | ||
142 | =item Borland C++ | |
143 | ||
144 | If you are using the Borland compiler, you will need dmake. | |
145 | (The make that Borland supplies is seriously crippled and will not | |
146 | work for MakeMaker builds.) | |
147 | ||
148 | See L</"Make"> above. | |
149 | ||
150 | =item Microsoft Visual C++ | |
151 | ||
152 | The nmake that comes with Visual C++ will suffice for building. | |
153 | You will need to run the VCVARS32.BAT file, usually found somewhere | |
b906aaa5 | 154 | like C:\Program Files\Microsoft Visual Studio\VC98\Bin. |
00808b83 | 155 | This will set your build environment. |
9baed986 LC |
156 | |
157 | You can also use dmake to build using Visual C++; provided, however, | |
158 | you set OSRELEASE to "microsft" (or whatever the directory name | |
159 | under which the Visual C dmake configuration lives) in your environment | |
160 | and edit win32/config.vc to change "make=nmake" into "make=dmake". The | |
161 | latter step is only essential if you want to use dmake as your default | |
162 | make for building extensions using MakeMaker. | |
163 | ||
2a46176f | 164 | =item Microsoft Visual C++ 2008/2010 Express Edition |
4a3cf07b | 165 | |
2a46176f SH |
166 | These free versions of Visual C++ 2008/2010 Professional contain the same |
167 | compilers and linkers that ship with the full versions, and also contain | |
168 | everything necessary to build Perl, rather than requiring a separate download | |
169 | of the Windows SDK like previous versions did. | |
4a3cf07b | 170 | |
2a46176f | 171 | These packages can be downloaded by searching in the Download Center at |
42d76a89 | 172 | L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact |
cb644b64 SH |
173 | links to these packages has proven a pointless task because the links keep on |
174 | changing so often.) | |
4a3cf07b | 175 | |
2a46176f | 176 | Install Visual C++ 2008/2010 Express, then setup your environment using, e.g. |
4a3cf07b | 177 | |
2a46176f | 178 | C:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools\vsvars32.bat |
4a3cf07b SH |
179 | |
180 | (assuming the default installation location was chosen). | |
181 | ||
182 | Perl should now build using the win32/Makefile. You will need to edit that | |
2a46176f | 183 | file to set CCTYPE to MSVC90FREE or MSVC100FREE first. |
4a3cf07b | 184 | |
1c847d4b SH |
185 | =item Microsoft Visual C++ 2005 Express Edition |
186 | ||
1c847d4b SH |
187 | This free version of Visual C++ 2005 Professional contains the same compiler |
188 | and linker that ship with the full version, but doesn't contain everything | |
189 | necessary to build Perl. | |
190 | ||
b906aaa5 | 191 | You will also need to download the "Windows SDK" (the "Core SDK" and "MDAC |
1c847d4b SH |
192 | SDK" components are required) for more header files and libraries. |
193 | ||
194 | These packages can both be downloaded by searching in the Download Center at | |
42d76a89 | 195 | L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact |
1c847d4b SH |
196 | links to these packages has proven a pointless task because the links keep on |
197 | changing so often.) | |
198 | ||
b906aaa5 | 199 | Try to obtain the latest version of the Windows SDK. Sometimes these packages |
1c847d4b SH |
200 | contain a particular Windows OS version in their name, but actually work on |
201 | other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK" | |
202 | also runs on Windows XP SP2 and Windows 2000. | |
203 | ||
1c847d4b SH |
204 | Install Visual C++ 2005 first, then the Platform SDK. Setup your environment |
205 | as follows (assuming default installation locations were chosen): | |
206 | ||
4246aec1 | 207 | SET PlatformSDKDir=C:\Program Files\Microsoft Platform SDK |
1c847d4b | 208 | |
4246aec1 | 209 | SET PATH=%SystemRoot%\system32;%SystemRoot%;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;C:\Program Files\Microsoft Visual Studio 8\VC\BIN;C:\Program Files\Microsoft Visual Studio 8\Common7\Tools;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;%PlatformSDKDir%\Bin |
1c847d4b | 210 | |
4246aec1 MH |
211 | SET INCLUDE=C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE;%PlatformSDKDir%\include |
212 | ||
213 | SET LIB=C:\Program Files\Microsoft Visual Studio 8\VC\LIB;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\lib;%PlatformSDKDir%\lib | |
1c847d4b SH |
214 | |
215 | SET LIBPATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 | |
216 | ||
4246aec1 MH |
217 | (The PlatformSDKDir might need to be set differently depending on which version |
218 | you are using. Earlier versions installed into "C:\Program Files\Microsoft SDK", | |
219 | while the latest versions install into version-specific locations such as | |
220 | "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2".) | |
221 | ||
1c847d4b SH |
222 | Perl should now build using the win32/Makefile. You will need to edit that |
223 | file to set | |
224 | ||
225 | CCTYPE = MSVC80FREE | |
226 | ||
227 | and to set CCHOME, CCINCDIR and CCLIBDIR as per the environment setup above. | |
228 | ||
7241fd28 SH |
229 | =item Microsoft Visual C++ Toolkit 2003 |
230 | ||
231 | This free toolkit contains the same compiler and linker that ship with | |
1c847d4b | 232 | Visual C++ .NET 2003 Professional, but doesn't contain everything |
7241fd28 SH |
233 | necessary to build Perl. |
234 | ||
235 | You will also need to download the "Platform SDK" (the "Core SDK" and "MDAC | |
236 | SDK" components are required) for header files, libraries and rc.exe, and | |
237 | ".NET Framework SDK" for more libraries and nmake.exe. Note that the latter | |
238 | (which also includes the free compiler and linker) requires the ".NET | |
239 | Framework Redistributable" to be installed first. This can be downloaded and | |
240 | installed separately, but is included in the "Visual C++ Toolkit 2003" anyway. | |
241 | ||
242 | These packages can all be downloaded by searching in the Download Center at | |
42d76a89 | 243 | L<http://www.microsoft.com/downloads/search.aspx?displaylang=en>. (Providing exact |
1b4f0359 SH |
244 | links to these packages has proven a pointless task because the links keep on |
245 | changing so often.) | |
246 | ||
b906aaa5 | 247 | Try to obtain the latest version of the Windows SDK. Sometimes these packages |
1b4f0359 | 248 | contain a particular Windows OS version in their name, but actually work on |
1c847d4b | 249 | other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK" |
1b4f0359 | 250 | also runs on Windows XP SP2 and Windows 2000. |
7241fd28 | 251 | |
7241fd28 SH |
252 | Install the Toolkit first, then the Platform SDK, then the .NET Framework SDK. |
253 | Setup your environment as follows (assuming default installation locations | |
254 | were chosen): | |
255 | ||
4246aec1 MH |
256 | SET PlatformSDKDir=C:\Program Files\Microsoft Platform SDK |
257 | ||
258 | SET PATH=%SystemRoot%\system32;%SystemRoot%;C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PlatformSDKDir%\Bin;C:\Program Files\Microsoft.NET\SDK\v1.1\Bin | |
259 | ||
260 | SET INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit 2003\include;%PlatformSDKDir%\include;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include | |
1c847d4b | 261 | |
4246aec1 | 262 | SET LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;%PlatformSDKDir%\lib;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib |
1c847d4b | 263 | |
4246aec1 MH |
264 | (The PlatformSDKDir might need to be set differently depending on which version |
265 | you are using. Earlier versions installed into "C:\Program Files\Microsoft SDK", | |
266 | while the latest versions install into version-specific locations such as | |
267 | "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2".) | |
7241fd28 SH |
268 | |
269 | Several required files will still be missing: | |
270 | ||
271 | =over 4 | |
272 | ||
273 | =item * | |
274 | ||
275 | cvtres.exe is required by link.exe when using a .res file. It is actually | |
276 | installed by the .NET Framework SDK, but into a location such as the | |
277 | following: | |
278 | ||
279 | C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 | |
280 | ||
4246aec1 | 281 | Copy it from there to %PlatformSDKDir%\Bin |
7241fd28 SH |
282 | |
283 | =item * | |
284 | ||
285 | lib.exe is normally used to build libraries, but link.exe with the /lib | |
f21bc467 MM |
286 | option also works, so change win32/config.vc to use it instead: |
287 | ||
288 | Change the line reading: | |
289 | ||
290 | ar='lib' | |
291 | ||
292 | to: | |
293 | ||
294 | ar='link /lib' | |
295 | ||
296 | It may also be useful to create a batch file called lib.bat in | |
7241fd28 SH |
297 | C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin containing: |
298 | ||
299 | @echo off | |
300 | link /lib %* | |
301 | ||
f21bc467 MM |
302 | for the benefit of any naughty C extension modules that you might want to build |
303 | later which explicitly reference "lib" rather than taking their value from | |
304 | $Config{ar}. | |
7241fd28 SH |
305 | |
306 | =item * | |
307 | ||
308 | setargv.obj is required to build perlglob.exe (and perl.exe if the USE_SETARGV | |
309 | option is enabled). The Platform SDK supplies this object file in source form | |
4246aec1 | 310 | in %PlatformSDKDir%\src\crt. Copy setargv.c, cruntime.h and |
7241fd28 SH |
311 | internal.h from there to some temporary location and build setargv.obj using |
312 | ||
313 | cl.exe /c /I. /D_CRTBLD setargv.c | |
314 | ||
4246aec1 | 315 | Then copy setargv.obj to %PlatformSDKDir%\lib |
7241fd28 | 316 | |
f21bc467 MM |
317 | Alternatively, if you don't need perlglob.exe and don't need to enable the |
318 | USE_SETARGV option then you can safely just remove all mention of $(GLOBEXE) | |
319 | from win32/Makefile and setargv.obj won't be required anyway. | |
320 | ||
7241fd28 SH |
321 | =back |
322 | ||
323 | Perl should now build using the win32/Makefile. You will need to edit that | |
da2c7419 SH |
324 | file to set |
325 | ||
326 | CCTYPE = MSVC70FREE | |
327 | ||
328 | and to set CCHOME, CCINCDIR and CCLIBDIR as per the environment setup above. | |
7241fd28 | 329 | |
9baed986 LC |
330 | =item Microsoft Platform SDK 64-bit Compiler |
331 | ||
332 | The nmake that comes with the Platform SDK will suffice for building | |
333 | Perl. Make sure you are building within one of the "Build Environment" | |
334 | shells available after you install the Platform SDK from the Start Menu. | |
335 | ||
e2736246 | 336 | =item MinGW release 3 with gcc |
9baed986 | 337 | |
ceb0c681 JD |
338 | Perl can be compiled with gcc from MinGW release 3 and later (using gcc 3.2.x |
339 | and later). It can be downloaded here: | |
9baed986 | 340 | |
42d76a89 | 341 | L<http://www.mingw.org/> |
7c5b6093 | 342 | |
9baed986 LC |
343 | You also need dmake. See L</"Make"> above on how to get it. |
344 | ||
9baed986 LC |
345 | =back |
346 | ||
347 | =head2 Building | |
348 | ||
349 | =over 4 | |
350 | ||
351 | =item * | |
352 | ||
353 | Make sure you are in the "win32" subdirectory under the perl toplevel. | |
354 | This directory contains a "Makefile" that will work with | |
b906aaa5 | 355 | versions of nmake that come with Visual C++ or the Windows SDK, and |
9baed986 | 356 | a dmake "makefile.mk" that will work for all supported compilers. The |
00808b83 | 357 | defaults in the dmake makefile are setup to build using MinGW/gcc. |
9baed986 LC |
358 | |
359 | =item * | |
360 | ||
dbd54a9f | 361 | Edit the makefile.mk (or Makefile, if you're using nmake) and change |
9baed986 LC |
362 | the values of INST_DRV and INST_TOP. You can also enable various |
363 | build flags. These are explained in the makefiles. | |
364 | ||
2b1846f4 SH |
365 | Note that it is generally not a good idea to try to build a perl with |
366 | INST_DRV and INST_TOP set to a path that already exists from a previous | |
367 | build. In particular, this may cause problems with the | |
368 | lib/ExtUtils/t/Embed.t test, which attempts to build a test program and | |
369 | may end up building against the installed perl's lib/CORE directory rather | |
370 | than the one being tested. | |
371 | ||
dbd54a9f | 372 | You will have to make sure that CCTYPE is set correctly and that |
fa58a56f S |
373 | CCHOME points to wherever you installed your compiler. If building with |
374 | gcc-4.x.x, you'll also need to uncomment the assignment to GCC_4XX and | |
375 | uncomment the assignment to the appropriate GCCHELPERDLL in the makefile.mk. | |
376 | ||
377 | If building with the cross-compiler provided by | |
378 | mingw-w64.sourceforge.net you'll need to uncomment the line that sets | |
379 | GCCCROSS in the makefile.mk. Do this only if it's the cross-compiler - ie | |
380 | only if the bin folder doesn't contain a gcc.exe. (The cross-compiler | |
381 | does not provide a gcc.exe, g++.exe, ar.exe, etc. Instead, all of these | |
382 | executables are prefixed with 'x86_64-w64-mingw32-'.) | |
9baed986 LC |
383 | |
384 | The default value for CCHOME in the makefiles for Visual C++ | |
385 | may not be correct for some versions. Make sure the default exists | |
386 | and is valid. | |
387 | ||
da2c7419 SH |
388 | You may also need to comment out the C<DELAYLOAD = ...> line in the |
389 | Makefile if you're using VC++ 6.0 without the latest service pack and | |
390 | the linker reports an internal error. | |
dbd54a9f | 391 | |
dbd54a9f VK |
392 | If you want build some core extensions statically into perl's dll, specify |
393 | them in the STATIC_EXT macro. | |
394 | ||
9baed986 LC |
395 | Be sure to read the instructions near the top of the makefiles carefully. |
396 | ||
397 | =item * | |
398 | ||
399 | Type "dmake" (or "nmake" if you are using that make). | |
400 | ||
401 | This should build everything. Specifically, it will create perl.exe, | |
cb47d8a5 | 402 | perl513.dll at the perl toplevel, and various other extension dll's |
9baed986 LC |
403 | under the lib\auto directory. If the build fails for any reason, make |
404 | sure you have done the previous steps correctly. | |
405 | ||
406 | =back | |
407 | ||
b906aaa5 | 408 | =head2 Testing Perl on Windows |
9baed986 LC |
409 | |
410 | Type "dmake test" (or "nmake test"). This will run most of the tests from | |
411 | the testsuite (many tests will be skipped). | |
412 | ||
b906aaa5 | 413 | There should be no test failures. |
9baed986 | 414 | |
ffc8a9ad SH |
415 | (If you're using VC++ 2010 then you will currently see several test failures, |
416 | as noted in the list of supported compilers above.) | |
417 | ||
9baed986 LC |
418 | Some test failures may occur if you use a command shell other than the |
419 | native "cmd.exe", or if you are building from a path that contains | |
420 | spaces. So don't do that. | |
421 | ||
422 | If you are running the tests from a emacs shell window, you may see | |
423 | failures in op/stat.t. Run "dmake test-notty" in that case. | |
424 | ||
425 | If you're using the Borland compiler, you may see a failure in op/taint.t | |
426 | arising from the inability to find the Borland Runtime DLLs on the system | |
427 | default path. You will need to copy the DLLs reported by the messages | |
428 | from where Borland chose to install it, into the Windows system directory | |
8cbe99e5 | 429 | (usually somewhere like C:\WINDOWS\SYSTEM32) and rerun the test. |
9baed986 LC |
430 | |
431 | If you're using Borland compiler versions 5.2 and below, you may run into | |
432 | problems finding the correct header files when building extensions. For | |
433 | example, building the "Tk" extension may fail because both perl and Tk | |
434 | contain a header file called "patchlevel.h". The latest Borland compiler | |
435 | (v5.5) is free of this misbehaviour, and it even supports an | |
436 | option -VI- for backward (bugward) compatibility for using the old Borland | |
437 | search algorithm to locate header files. | |
438 | ||
a6a21311 PEE |
439 | If you run the tests on a FAT partition, you may see some failures for |
440 | C<link()> related tests (I<op/write.t>, I<op/stat.t> ...). Testing on | |
441 | NTFS avoids these errors. | |
442 | ||
443 | Furthermore, you should make sure that during C<make test> you do not | |
444 | have any GNU tool packages in your path: some toolkits like Unixutils | |
445 | include some tools (C<type> for instance) which override the Windows | |
446 | ones and makes tests fail. Remove them from your path while testing to | |
447 | avoid these errors. | |
448 | ||
9baed986 LC |
449 | Please report any other failures as described under L<BUGS AND CAVEATS>. |
450 | ||
b906aaa5 | 451 | =head2 Installation of Perl on Windows |
9baed986 LC |
452 | |
453 | Type "dmake install" (or "nmake install"). This will put the newly | |
454 | built perl and the libraries under whatever C<INST_TOP> points to in the | |
455 | Makefile. It will also install the pod documentation under | |
00808b83 SH |
456 | C<$INST_TOP\$INST_VER\lib\pod> and HTML versions of the same under |
457 | C<$INST_TOP\$INST_VER\lib\pod\html>. | |
9baed986 | 458 | |
00808b83 SH |
459 | To use the Perl you just installed you will need to add a new entry to |
460 | your PATH environment variable: C<$INST_TOP\bin>, e.g. | |
9baed986 | 461 | |
00808b83 | 462 | set PATH=c:\perl\bin;%PATH% |
9baed986 | 463 | |
00808b83 SH |
464 | If you opted to uncomment C<INST_VER> and C<INST_ARCH> in the makefile |
465 | then the installation structure is a little more complicated and you will | |
466 | need to add two new PATH components instead: C<$INST_TOP\$INST_VER\bin> and | |
467 | C<$INST_TOP\$INST_VER\bin\$ARCHNAME>, e.g. | |
468 | ||
469 | set PATH=c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH% | |
9baed986 | 470 | |
b906aaa5 | 471 | =head2 Usage Hints for Perl on Windows |
9baed986 LC |
472 | |
473 | =over 4 | |
474 | ||
475 | =item Environment Variables | |
476 | ||
477 | The installation paths that you set during the build get compiled | |
478 | into perl, so you don't have to do anything additional to start | |
479 | using that perl (except add its location to your PATH variable). | |
480 | ||
481 | If you put extensions in unusual places, you can set PERL5LIB | |
482 | to a list of paths separated by semicolons where you want perl | |
483 | to look for libraries. Look for descriptions of other environment | |
484 | variables you can set in L<perlrun>. | |
485 | ||
486 | You can also control the shell that perl uses to run system() and | |
487 | backtick commands via PERL5SHELL. See L<perlrun>. | |
488 | ||
489 | Perl does not depend on the registry, but it can look up certain default | |
490 | values if you choose to put them there. Perl attempts to read entries from | |
491 | C<HKEY_CURRENT_USER\Software\Perl> and C<HKEY_LOCAL_MACHINE\Software\Perl>. | |
492 | Entries in the former override entries in the latter. One or more of the | |
493 | following entries (of type REG_SZ or REG_EXPAND_SZ) may be set: | |
494 | ||
495 | lib-$] version-specific standard library path to add to @INC | |
496 | lib standard library path to add to @INC | |
497 | sitelib-$] version-specific site library path to add to @INC | |
498 | sitelib site library path to add to @INC | |
499 | vendorlib-$] version-specific vendor library path to add to @INC | |
500 | vendorlib vendor library path to add to @INC | |
501 | PERL* fallback for all %ENV lookups that begin with "PERL" | |
502 | ||
503 | Note the C<$]> in the above is not literal. Substitute whatever version | |
504 | of perl you want to honor that entry, e.g. C<5.6.0>. Paths must be | |
b906aaa5 | 505 | separated with semicolons, as usual on Windows. |
9baed986 LC |
506 | |
507 | =item File Globbing | |
508 | ||
509 | By default, perl handles file globbing using the File::Glob extension, | |
510 | which provides portable globbing. | |
511 | ||
512 | If you want perl to use globbing that emulates the quirks of DOS | |
513 | filename conventions, you might want to consider using File::DosGlob | |
514 | to override the internal glob() implementation. See L<File::DosGlob> for | |
515 | details. | |
516 | ||
517 | =item Using perl from the command line | |
518 | ||
519 | If you are accustomed to using perl from various command-line | |
520 | shells found in UNIX environments, you will be less than pleased | |
521 | with what Windows offers by way of a command shell. | |
522 | ||
523 | The crucial thing to understand about the Windows environment is that | |
524 | the command line you type in is processed twice before Perl sees it. | |
8cbe99e5 JD |
525 | First, your command shell (usually CMD.EXE) preprocesses the command |
526 | line, to handle redirection, environment variable expansion, and | |
527 | location of the executable to run. Then, the perl executable splits | |
528 | the remaining command line into individual arguments, using the | |
529 | C runtime library upon which Perl was built. | |
9baed986 LC |
530 | |
531 | It is particularly important to note that neither the shell nor the C | |
532 | runtime do any wildcard expansions of command-line arguments (so | |
533 | wildcards need not be quoted). Also, the quoting behaviours of the | |
534 | shell and the C runtime are rudimentary at best (and may, if you are | |
535 | using a non-standard shell, be inconsistent). The only (useful) quote | |
536 | character is the double quote ("). It can be used to protect spaces | |
537 | and other special characters in arguments. | |
538 | ||
8cbe99e5 | 539 | The Windows documentation has almost no description of how the |
9baed986 LC |
540 | quoting rules are implemented, but here are some general observations |
541 | based on experiments: The C runtime breaks arguments at spaces and | |
542 | passes them to programs in argc/argv. Double quotes can be used to | |
543 | prevent arguments with spaces in them from being split up. You can | |
544 | put a double quote in an argument by escaping it with a backslash and | |
545 | enclosing the whole argument within double quotes. The backslash and | |
546 | the pair of double quotes surrounding the argument will be stripped by | |
547 | the C runtime. | |
548 | ||
00808b83 | 549 | The file redirection characters "E<lt>", "E<gt>", and "|" can be quoted by |
9baed986 LC |
550 | double quotes (although there are suggestions that this may not always |
551 | be true). Single quotes are not treated as quotes by the shell or | |
552 | the C runtime, they don't get stripped by the shell (just to make | |
553 | this type of quoting completely useless). The caret "^" has also | |
554 | been observed to behave as a quoting character, but this appears | |
555 | to be a shell feature, and the caret is not stripped from the command | |
556 | line, so Perl still sees it (and the C runtime phase does not treat | |
557 | the caret as a quote character). | |
558 | ||
559 | Here are some examples of usage of the "cmd" shell: | |
560 | ||
561 | This prints two doublequotes: | |
562 | ||
563 | perl -e "print '\"\"' " | |
564 | ||
565 | This does the same: | |
566 | ||
567 | perl -e "print \"\\\"\\\"\" " | |
568 | ||
569 | This prints "bar" and writes "foo" to the file "blurch": | |
570 | ||
571 | perl -e "print 'foo'; print STDERR 'bar'" > blurch | |
572 | ||
573 | This prints "foo" ("bar" disappears into nowhereland): | |
574 | ||
575 | perl -e "print 'foo'; print STDERR 'bar'" 2> nul | |
576 | ||
577 | This prints "bar" and writes "foo" into the file "blurch": | |
578 | ||
579 | perl -e "print 'foo'; print STDERR 'bar'" 1> blurch | |
580 | ||
581 | This pipes "foo" to the "less" pager and prints "bar" on the console: | |
582 | ||
583 | perl -e "print 'foo'; print STDERR 'bar'" | less | |
584 | ||
585 | This pipes "foo\nbar\n" to the less pager: | |
586 | ||
587 | perl -le "print 'foo'; print STDERR 'bar'" 2>&1 | less | |
588 | ||
589 | This pipes "foo" to the pager and writes "bar" in the file "blurch": | |
590 | ||
591 | perl -e "print 'foo'; print STDERR 'bar'" 2> blurch | less | |
592 | ||
593 | ||
594 | Discovering the usefulness of the "command.com" shell on Windows 9x | |
595 | is left as an exercise to the reader :) | |
596 | ||
597 | One particularly pernicious problem with the 4NT command shell for | |
8cbe99e5 | 598 | Windows is that it (nearly) always treats a % character as indicating |
9baed986 LC |
599 | that environment variable expansion is needed. Under this shell, it is |
600 | therefore important to always double any % characters which you want | |
601 | Perl to see (for example, for hash variables), even when they are | |
602 | quoted. | |
603 | ||
604 | =item Building Extensions | |
605 | ||
606 | The Comprehensive Perl Archive Network (CPAN) offers a wealth | |
607 | of extensions, some of which require a C compiler to build. | |
42d76a89 | 608 | Look in L<http://www.cpan.org/> for more information on CPAN. |
9baed986 LC |
609 | |
610 | Note that not all of the extensions available from CPAN may work | |
b906aaa5 | 611 | in the Windows environment; you should check the information at |
42d76a89 | 612 | L<http://testers.cpan.org/> before investing too much effort into |
9baed986 LC |
613 | porting modules that don't readily build. |
614 | ||
615 | Most extensions (whether they require a C compiler or not) can | |
616 | be built, tested and installed with the standard mantra: | |
617 | ||
618 | perl Makefile.PL | |
619 | $MAKE | |
620 | $MAKE test | |
621 | $MAKE install | |
622 | ||
623 | where $MAKE is whatever 'make' program you have configured perl to | |
624 | use. Use "perl -V:make" to find out what this is. Some extensions | |
625 | may not provide a testsuite (so "$MAKE test" may not do anything or | |
626 | fail), but most serious ones do. | |
627 | ||
628 | It is important that you use a supported 'make' program, and | |
629 | ensure Config.pm knows about it. If you don't have nmake, you can | |
630 | either get dmake from the location mentioned earlier or get an | |
631 | old version of nmake reportedly available from: | |
632 | ||
42d76a89 | 633 | L<http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/nmake15.exe> |
9baed986 LC |
634 | |
635 | Another option is to use the make written in Perl, available from | |
636 | CPAN. | |
637 | ||
42d76a89 | 638 | L<http://www.cpan.org/modules/by-module/Make/> |
9baed986 LC |
639 | |
640 | You may also use dmake. See L</"Make"> above on how to get it. | |
641 | ||
642 | Note that MakeMaker actually emits makefiles with different syntax | |
643 | depending on what 'make' it thinks you are using. Therefore, it is | |
644 | important that one of the following values appears in Config.pm: | |
645 | ||
646 | make='nmake' # MakeMaker emits nmake syntax | |
647 | make='dmake' # MakeMaker emits dmake syntax | |
648 | any other value # MakeMaker emits generic make syntax | |
649 | (e.g GNU make, or Perl make) | |
650 | ||
651 | If the value doesn't match the 'make' program you want to use, | |
652 | edit Config.pm to fix it. | |
653 | ||
654 | If a module implements XSUBs, you will need one of the supported | |
655 | C compilers. You must make sure you have set up the environment for | |
656 | the compiler for command-line compilation. | |
657 | ||
658 | If a module does not build for some reason, look carefully for | |
659 | why it failed, and report problems to the module author. If | |
660 | it looks like the extension building support is at fault, report | |
661 | that with full details of how the build failed using the perlbug | |
662 | utility. | |
663 | ||
664 | =item Command-line Wildcard Expansion | |
665 | ||
666 | The default command shells on DOS descendant operating systems (such | |
667 | as they are) usually do not expand wildcard arguments supplied to | |
668 | programs. They consider it the application's job to handle that. | |
669 | This is commonly achieved by linking the application (in our case, | |
670 | perl) with startup code that the C runtime libraries usually provide. | |
671 | However, doing that results in incompatible perl versions (since the | |
672 | behavior of the argv expansion code differs depending on the | |
673 | compiler, and it is even buggy on some compilers). Besides, it may | |
674 | be a source of frustration if you use such a perl binary with an | |
675 | alternate shell that *does* expand wildcards. | |
676 | ||
677 | Instead, the following solution works rather well. The nice things | |
dbd54a9f | 678 | about it are 1) you can start using it right away; 2) it is more |
9baed986 LC |
679 | powerful, because it will do the right thing with a pattern like |
680 | */*/*.c; 3) you can decide whether you do/don't want to use it; and | |
dbd54a9f | 681 | 4) you can extend the method to add any customizations (or even |
9baed986 LC |
682 | entirely different kinds of wildcard expansion). |
683 | ||
684 | C:\> copy con c:\perl\lib\Wild.pm | |
685 | # Wild.pm - emulate shell @ARGV expansion on shells that don't | |
686 | use File::DosGlob; | |
687 | @ARGV = map { | |
688 | my @g = File::DosGlob::glob($_) if /[*?]/; | |
689 | @g ? @g : $_; | |
690 | } @ARGV; | |
691 | 1; | |
692 | ^Z | |
693 | C:\> set PERL5OPT=-MWild | |
694 | C:\> perl -le "for (@ARGV) { print }" */*/perl*.c | |
695 | p4view/perl/perl.c | |
696 | p4view/perl/perlio.c | |
697 | p4view/perl/perly.c | |
698 | perl5.005/win32/perlglob.c | |
699 | perl5.005/win32/perllib.c | |
700 | perl5.005/win32/perlglob.c | |
701 | perl5.005/win32/perllib.c | |
702 | perl5.005/win32/perlglob.c | |
703 | perl5.005/win32/perllib.c | |
704 | ||
705 | Note there are two distinct steps there: 1) You'll have to create | |
706 | Wild.pm and put it in your perl lib directory. 2) You'll need to | |
707 | set the PERL5OPT environment variable. If you want argv expansion | |
708 | to be the default, just set PERL5OPT in your default startup | |
709 | environment. | |
710 | ||
711 | If you are using the Visual C compiler, you can get the C runtime's | |
712 | command line wildcard expansion built into perl binary. The resulting | |
713 | binary will always expand unquoted command lines, which may not be | |
714 | what you want if you use a shell that does that for you. The expansion | |
715 | done is also somewhat less powerful than the approach suggested above. | |
716 | ||
9baed986 LC |
717 | =item Notes on 64-bit Windows |
718 | ||
719 | Windows .NET Server supports the LLP64 data model on the Intel Itanium | |
720 | architecture. | |
721 | ||
722 | The LLP64 data model is different from the LP64 data model that is the | |
723 | norm on 64-bit Unix platforms. In the former, C<int> and C<long> are | |
724 | both 32-bit data types, while pointers are 64 bits wide. In addition, | |
725 | there is a separate 64-bit wide integral type, C<__int64>. In contrast, | |
726 | the LP64 data model that is pervasive on Unix platforms provides C<int> | |
727 | as the 32-bit type, while both the C<long> type and pointers are of | |
728 | 64-bit precision. Note that both models provide for 64-bits of | |
729 | addressability. | |
730 | ||
731 | 64-bit Windows running on Itanium is capable of running 32-bit x86 | |
732 | binaries transparently. This means that you could use a 32-bit build | |
733 | of Perl on a 64-bit system. Given this, why would one want to build | |
734 | a 64-bit build of Perl? Here are some reasons why you would bother: | |
735 | ||
00808b83 SH |
736 | =over |
737 | ||
9baed986 LC |
738 | =item * |
739 | ||
740 | A 64-bit native application will run much more efficiently on | |
741 | Itanium hardware. | |
742 | ||
743 | =item * | |
744 | ||
745 | There is no 2GB limit on process size. | |
746 | ||
747 | =item * | |
748 | ||
749 | Perl automatically provides large file support when built under | |
750 | 64-bit Windows. | |
751 | ||
752 | =item * | |
753 | ||
754 | Embedding Perl inside a 64-bit application. | |
755 | ||
756 | =back | |
757 | ||
00808b83 SH |
758 | =back |
759 | ||
9baed986 LC |
760 | =head2 Running Perl Scripts |
761 | ||
762 | Perl scripts on UNIX use the "#!" (a.k.a "shebang") line to | |
763 | indicate to the OS that it should execute the file using perl. | |
b906aaa5 | 764 | Windows has no comparable means to indicate arbitrary files are |
9baed986 LC |
765 | executables. |
766 | ||
767 | Instead, all available methods to execute plain text files on | |
b906aaa5 | 768 | Windows rely on the file "extension". There are three methods |
9baed986 LC |
769 | to use this to execute perl scripts: |
770 | ||
771 | =over 8 | |
772 | ||
773 | =item 1 | |
774 | ||
8cbe99e5 JD |
775 | There is a facility called "file extension associations". This can be |
776 | manipulated via the two commands "assoc" and "ftype" that come | |
777 | standard with Windows. Type "ftype /?" for a complete example of how | |
778 | to set this up for perl scripts (Say what? You thought Windows | |
779 | wasn't perl-ready? :). | |
9baed986 LC |
780 | |
781 | =item 2 | |
782 | ||
783 | Since file associations don't work everywhere, and there are | |
784 | reportedly bugs with file associations where it does work, the | |
785 | old method of wrapping the perl script to make it look like a | |
786 | regular batch file to the OS, may be used. The install process | |
787 | makes available the "pl2bat.bat" script which can be used to wrap | |
788 | perl scripts into batch files. For example: | |
789 | ||
790 | pl2bat foo.pl | |
791 | ||
792 | will create the file "FOO.BAT". Note "pl2bat" strips any | |
793 | .pl suffix and adds a .bat suffix to the generated file. | |
794 | ||
795 | If you use the 4DOS/NT or similar command shell, note that | |
796 | "pl2bat" uses the "%*" variable in the generated batch file to | |
797 | refer to all the command line arguments, so you may need to make | |
798 | sure that construct works in batch files. As of this writing, | |
799 | 4DOS/NT users will need a "ParameterChar = *" statement in their | |
800 | 4NT.INI file or will need to execute "setdos /p*" in the 4DOS/NT | |
801 | startup file to enable this to work. | |
802 | ||
803 | =item 3 | |
804 | ||
805 | Using "pl2bat" has a few problems: the file name gets changed, | |
806 | so scripts that rely on C<$0> to find what they must do may not | |
807 | run properly; running "pl2bat" replicates the contents of the | |
808 | original script, and so this process can be maintenance intensive | |
809 | if the originals get updated often. A different approach that | |
810 | avoids both problems is possible. | |
811 | ||
812 | A script called "runperl.bat" is available that can be copied | |
813 | to any filename (along with the .bat suffix). For example, | |
814 | if you call it "foo.bat", it will run the file "foo" when it is | |
b906aaa5 | 815 | executed. Since you can run batch files on Windows platforms simply |
9baed986 LC |
816 | by typing the name (without the extension), this effectively |
817 | runs the file "foo", when you type either "foo" or "foo.bat". | |
818 | With this method, "foo.bat" can even be in a different location | |
819 | than the file "foo", as long as "foo" is available somewhere on | |
820 | the PATH. If your scripts are on a filesystem that allows symbolic | |
821 | links, you can even avoid copying "runperl.bat". | |
822 | ||
823 | Here's a diversion: copy "runperl.bat" to "runperl", and type | |
824 | "runperl". Explain the observed behavior, or lack thereof. :) | |
825 | Hint: .gnidnats llits er'uoy fi ,"lrepnur" eteled :tniH | |
826 | ||
00808b83 SH |
827 | =back |
828 | ||
829 | =head2 Miscellaneous Things | |
9baed986 LC |
830 | |
831 | A full set of HTML documentation is installed, so you should be | |
832 | able to use it if you have a web browser installed on your | |
833 | system. | |
834 | ||
835 | C<perldoc> is also a useful tool for browsing information contained | |
836 | in the documentation, especially in conjunction with a pager | |
b906aaa5 | 837 | like C<less> (recent versions of which have Windows support). You may |
9baed986 LC |
838 | have to set the PAGER environment variable to use a specific pager. |
839 | "perldoc -f foo" will print information about the perl operator | |
840 | "foo". | |
841 | ||
13ee867e BD |
842 | One common mistake when using this port with a GUI library like C<Tk> |
843 | is assuming that Perl's normal behavior of opening a command-line | |
844 | window will go away. This isn't the case. If you want to start a copy | |
845 | of C<perl> without opening a command-line window, use the C<wperl> | |
846 | executable built during the installation process. Usage is exactly | |
b906aaa5 | 847 | the same as normal C<perl> on Windows, except that options like C<-h> |
13ee867e BD |
848 | don't work (since they need a command-line window to print to). |
849 | ||
9baed986 LC |
850 | If you find bugs in perl, you can run C<perlbug> to create a |
851 | bug report (you may have to send it manually if C<perlbug> cannot | |
852 | find a mailer on your system). | |
853 | ||
9baed986 LC |
854 | =head1 BUGS AND CAVEATS |
855 | ||
dbd54a9f VK |
856 | Norton AntiVirus interferes with the build process, particularly if |
857 | set to "AutoProtect, All Files, when Opened". Unlike large applications | |
858 | the perl build process opens and modifies a lot of files. Having the | |
9baed986 LC |
859 | the AntiVirus scan each and every one slows build the process significantly. |
860 | Worse, with PERLIO=stdio the build process fails with peculiar messages | |
dbd54a9f | 861 | as the virus checker interacts badly with miniperl.exe writing configure |
9baed986 LC |
862 | files (it seems to either catch file part written and treat it as suspicious, |
863 | or virus checker may have it "locked" in a way which inhibits miniperl | |
dbd54a9f | 864 | updating it). The build does complete with |
9baed986 LC |
865 | |
866 | set PERLIO=perlio | |
867 | ||
868 | but that may be just luck. Other AntiVirus software may have similar issues. | |
869 | ||
870 | Some of the built-in functions do not act exactly as documented in | |
871 | L<perlfunc>, and a few are not implemented at all. To avoid | |
872 | surprises, particularly if you have had prior exposure to Perl | |
873 | in other operating environments or if you intend to write code | |
00808b83 | 874 | that will be portable to other environments, see L<perlport> |
9baed986 LC |
875 | for a reasonably definitive list of these differences. |
876 | ||
877 | Not all extensions available from CPAN may build or work properly | |
b906aaa5 | 878 | in the Windows environment. See L</"Building Extensions">. |
9baed986 LC |
879 | |
880 | Most C<socket()> related calls are supported, but they may not | |
881 | behave as on Unix platforms. See L<perlport> for the full list. | |
882 | ||
883 | Signal handling may not behave as on Unix platforms (where it | |
884 | doesn't exactly "behave", either :). For instance, calling C<die()> | |
885 | or C<exit()> from signal handlers will cause an exception, since most | |
b906aaa5 | 886 | implementations of C<signal()> on Windows are severely crippled. |
9baed986 LC |
887 | Thus, signals may work only for simple things like setting a flag |
888 | variable in the handler. Using signals under this port should | |
889 | currently be considered unsupported. | |
890 | ||
dbd54a9f | 891 | Please send detailed descriptions of any problems and solutions that |
00808b83 SH |
892 | you may find to E<lt>F<perlbug@perl.org>E<gt>, along with the output |
893 | produced by C<perl -V>. | |
9baed986 | 894 | |
e84ac4e2 SH |
895 | =head1 ACKNOWLEDGEMENTS |
896 | ||
897 | The use of a camel with the topic of Perl is a trademark | |
898 | of O'Reilly and Associates, Inc. Used with permission. | |
899 | ||
9baed986 LC |
900 | =head1 AUTHORS |
901 | ||
902 | =over 4 | |
903 | ||
904 | =item Gary Ng E<lt>71564.1743@CompuServe.COME<gt> | |
905 | ||
906 | =item Gurusamy Sarathy E<lt>gsar@activestate.comE<gt> | |
907 | ||
908 | =item Nick Ing-Simmons E<lt>nick@ing-simmons.netE<gt> | |
909 | ||
2bfd3252 SH |
910 | =item Jan Dubois E<lt>jand@activestate.comE<gt> |
911 | ||
2a46176f | 912 | =item Steve Hay E<lt>steve.m.hay@googlemail.comE<gt> |
2bfd3252 | 913 | |
9baed986 LC |
914 | =back |
915 | ||
2bfd3252 | 916 | This document is maintained by Jan Dubois. |
9baed986 LC |
917 | |
918 | =head1 SEE ALSO | |
919 | ||
920 | L<perl> | |
921 | ||
922 | =head1 HISTORY | |
923 | ||
924 | This port was originally contributed by Gary Ng around 5.003_24, | |
925 | and borrowed from the Hip Communications port that was available | |
926 | at the time. Various people have made numerous and sundry hacks | |
927 | since then. | |
928 | ||
929 | Borland support was added in 5.004_01 (Gurusamy Sarathy). | |
930 | ||
931 | GCC/mingw32 support was added in 5.005 (Nick Ing-Simmons). | |
932 | ||
933 | Support for PERL_OBJECT was added in 5.005 (ActiveState Tool Corp). | |
934 | ||
935 | Support for fork() emulation was added in 5.6 (ActiveState Tool Corp). | |
936 | ||
937 | Win9x support was added in 5.6 (Benjamin Stuhl). | |
938 | ||
939 | Support for 64-bit Windows added in 5.8 (ActiveState Corp). | |
940 | ||
2a46176f | 941 | Last updated: 18 November 2010 |
9baed986 LC |
942 | |
943 | =cut |