Commit | Line | Data |
---|---|---|
68dc0745 | 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 | ||
5aabfad6 | 7 | perlwin32 - Perl under Win32 |
68dc0745 | 8 | |
9 | =head1 SYNOPSIS | |
10 | ||
63f87e49 GS |
11 | These are instructions for building Perl under Windows (9x, NT and |
12 | 2000). | |
68dc0745 | 13 | |
14 | =head1 DESCRIPTION | |
15 | ||
3fe9a6f1 | 16 | Before you start, you should glance through the README file |
68dc0745 | 17 | found in the top-level directory where the Perl distribution |
18 | was extracted. Make sure you read and understand the terms under | |
19 | which this software is being distributed. | |
20 | ||
f7c603cb | 21 | Also make sure you read L<BUGS AND CAVEATS> below for the |
68dc0745 | 22 | known limitations of this port. |
23 | ||
24 | The INSTALL file in the perl top-level has much information that is | |
25 | only relevant to people building Perl on Unix-like systems. In | |
26 | particular, you can safely ignore any information that talks about | |
27 | "Configure". | |
28 | ||
7bac28a0 | 29 | You may also want to look at two other options for building |
873b149f | 30 | a perl that will work on Windows NT: the README.cygwin and |
3e3baf6d TB |
31 | README.os2 files, which each give a different set of rules to build |
32 | a Perl that will work on Win32 platforms. Those two methods will | |
7bac28a0 | 33 | probably enable you to build a more Unix-compatible perl, but you |
34 | will also need to download and use various other build-time and | |
35 | run-time support software described in those files. | |
68dc0745 | 36 | |
37 | This set of instructions is meant to describe a so-called "native" | |
38 | port of Perl to Win32 platforms. The resulting Perl requires no | |
39 | additional software to run (other than what came with your operating | |
9036c72f GS |
40 | system). Currently, this port is capable of using one of the |
41 | following compilers: | |
42 | ||
43 | Borland C++ version 5.02 or later | |
44 | Microsoft Visual C++ version 4.2 or later | |
5db10396 | 45 | Mingw32 with GCC version 2.95.2 or better |
9036c72f | 46 | |
5db10396 GS |
47 | The last of these is a high quality freeware compiler. Support |
48 | for it is still experimental. (Older versions of GCC are known | |
49 | not to work.) | |
5aabfad6 | 50 | |
51 | This port currently supports MakeMaker (the set of modules that | |
52 | is used to build extensions to perl). Therefore, you should be | |
53 | able to build and install most extensions found in the CPAN sites. | |
c90c0ff4 | 54 | See L<Usage Hints> below for general hints about this. |
68dc0745 | 55 | |
56 | =head2 Setting Up | |
57 | ||
58 | =over 4 | |
59 | ||
63f87e49 GS |
60 | =item Make |
61 | ||
62 | You need a "make" program to build the sources. If you are using | |
63 | Visual C++ under Windows NT or 2000, nmake will work. All other | |
64 | builds need dmake. | |
65 | ||
66 | dmake is a freely available make that has very nice macro features | |
67 | and parallelability. | |
68 | ||
69 | A port of dmake for Windows is available from: | |
70 | ||
71 | http://www.cpan.org/authors/id/GSAR/dmake-4.1pl1-win32.zip | |
72 | ||
73 | (This is a fixed version of original dmake sources obtained from | |
74 | http://www.wticorp.com/dmake/. As of version 4.1PL1, the original | |
75 | sources did not build as shipped, and had various other problems. | |
76 | A patch is included in the above fixed version.) | |
77 | ||
78 | Fetch and install dmake somewhere on your path (follow the instructions | |
79 | in the README.NOW file). | |
80 | ||
3e3baf6d | 81 | =item Command Shell |
68dc0745 | 82 | |
26618a56 GS |
83 | Use the default "cmd" shell that comes with NT. Some versions of the |
84 | popular 4DOS/NT shell have incompatibilities that may cause you trouble. | |
85 | If the build fails under that shell, try building again with the cmd | |
63f87e49 | 86 | shell. |
26618a56 | 87 | |
a2293a43 | 88 | The nmake Makefile also has known incompatibilities with the |
63f87e49 GS |
89 | "command.com" shell that comes with Windows 9x. You will need to |
90 | use dmake and makefile.mk to build under Windows 9x. | |
8ec44883 GS |
91 | |
92 | The surest way to build it is on Windows NT, using the cmd shell. | |
68dc0745 | 93 | |
a8deba26 GS |
94 | Make sure the path to the build directory does not contain spaces. The |
95 | build usually works in this circumstance, but some tests will fail. | |
96 | ||
3e3baf6d TB |
97 | =item Borland C++ |
98 | ||
63f87e49 | 99 | If you are using the Borland compiler, you will need dmake. |
3e3baf6d | 100 | (The make that Borland supplies is seriously crippled, and will not |
26618a56 GS |
101 | work for MakeMaker builds.) |
102 | ||
63f87e49 | 103 | See L/"Make"> above. |
3e3baf6d TB |
104 | |
105 | =item Microsoft Visual C++ | |
68dc0745 | 106 | |
8ec44883 | 107 | The nmake that comes with Visual C++ will suffice for building. |
9036c72f GS |
108 | You will need to run the VCVARS32.BAT file usually found somewhere |
109 | like C:\MSDEV4.2\BIN. This will set your build environment. | |
68dc0745 | 110 | |
26618a56 GS |
111 | You can also use dmake to build using Visual C++, provided: |
112 | you set OSRELEASE to "microsft" (or whatever the directory name | |
113 | under which the Visual C dmake configuration lives) in your environment, | |
114 | and edit win32/config.vc to change "make=nmake" into "make=dmake". The | |
115 | latter step is only essential if you want to use dmake as your default | |
116 | make for building extensions using MakeMaker. | |
3e3baf6d | 117 | |
5db10396 | 118 | =item Mingw32 with GCC |
9036c72f | 119 | |
5db10396 | 120 | GCC-2.95.2 binaries can be downloaded from: |
9036c72f GS |
121 | |
122 | ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/ | |
68dc0745 | 123 | |
5db10396 | 124 | The GCC-2.95.2 bundle comes with Mingw32 libraries and headers. |
68dc0745 | 125 | |
7a1f88ac GS |
126 | Make sure you install the binaries that work with MSVCRT.DLL as indicated |
127 | in the README for the GCC bundle. You may need to set up a few environment | |
128 | variables (usually run from a batch file). | |
68dc0745 | 129 | |
4375e838 GS |
130 | The version of gcc-2.95.2-msvcrt.exe released 7 November 1999 left out |
131 | a fix for certain command line quotes, so be sure to download and install | |
132 | fixes/quote-fix-msvcrt.exe too. | |
133 | ||
63f87e49 | 134 | You also need dmake. See L</"Make"> above on how to get it. |
ee4d903c | 135 | |
68dc0745 | 136 | =back |
137 | ||
137443ea | 138 | =head2 Building |
68dc0745 | 139 | |
140 | =over 4 | |
141 | ||
142 | =item * | |
143 | ||
68dc0745 | 144 | Make sure you are in the "win32" subdirectory under the perl toplevel. |
137443ea | 145 | This directory contains a "Makefile" that will work with |
8ec44883 | 146 | versions of nmake that come with Visual C++, and a dmake "makefile.mk" |
9036c72f | 147 | that will work for all supported compilers. The defaults in the dmake |
63f87e49 | 148 | makefile are setup to build using the GCC compiler. |
68dc0745 | 149 | |
150 | =item * | |
151 | ||
9036c72f GS |
152 | Edit the makefile.mk (or Makefile, if using nmake) and change the values |
153 | of INST_DRV and INST_TOP. You can also enable various build | |
63f87e49 GS |
154 | flags. These are explained in the makefiles. |
155 | ||
156 | You will have to make sure CCTYPE is set correctly, and CCHOME points | |
157 | to wherever you installed your compiler. | |
158 | ||
159 | The default value for CCHOME in the makefiles for Visual C++ | |
160 | may not be correct for some versions. Make sure the default exists | |
161 | and is valid. | |
9036c72f | 162 | |
26618a56 GS |
163 | If you have either the source or a library that contains des_fcrypt(), |
164 | enable the appropriate option in the makefile. des_fcrypt() is not | |
165 | bundled with the distribution due to US Government restrictions | |
166 | on the export of cryptographic software. Nevertheless, this routine | |
58231d39 | 167 | is part of the "libdes" library (written by Eric Young) which is widely |
26618a56 GS |
168 | available worldwide, usually along with SSLeay (for example: |
169 | "ftp://fractal.mta.ca/pub/crypto/SSLeay/DES/"). Set CRYPT_SRC to the | |
170 | name of the file that implements des_fcrypt(). Alternatively, if | |
171 | you have built a library that contains des_fcrypt(), you can set | |
2d77217b GS |
172 | CRYPT_LIB to point to the library name. The location above contains |
173 | many versions of the "libdes" library, all with slightly different | |
174 | implementations of des_fcrypt(). Older versions have a single, | |
175 | self-contained file (fcrypt.c) that implements crypt(), so they may be | |
176 | easier to use. A patch against the fcrypt.c found in libdes-3.06 is | |
177 | in des_fcrypt.patch. | |
26618a56 GS |
178 | |
179 | Perl will also build without des_fcrypt(), but the crypt() builtin will | |
180 | fail at run time. | |
c90c0ff4 | 181 | |
63f87e49 | 182 | Be sure to read the instructions near the top of the makefiles carefully. |
9036c72f | 183 | |
68dc0745 | 184 | =item * |
185 | ||
9036c72f | 186 | Type "dmake" (or "nmake" if you are using that make). |
68dc0745 | 187 | |
137443ea | 188 | This should build everything. Specifically, it will create perl.exe, |
63f87e49 GS |
189 | perl56.dll at the perl toplevel, and various other extension dll's |
190 | under the lib\auto directory. If the build fails for any reason, make | |
191 | sure you have done the previous steps correctly. | |
156a3eb7 | 192 | |
68dc0745 | 193 | =back |
194 | ||
195 | =head2 Testing | |
196 | ||
9036c72f | 197 | Type "dmake test" (or "nmake test"). This will run most of the tests from |
807d88e1 | 198 | the testsuite (many tests will be skipped). |
68dc0745 | 199 | |
532fa798 GS |
200 | There should be no test failures when running under Windows NT 4.0 or |
201 | Windows 2000. Many tests I<will> fail under Windows 9x due to the inferior | |
202 | command shell. | |
807d88e1 GS |
203 | |
204 | Some test failures may occur if you use a command shell other than the | |
205 | native "cmd.exe", or if you are building from a path that contains | |
206 | spaces. So don't do that. | |
68dc0745 | 207 | |
328c22fc GS |
208 | If you are running the tests from a emacs shell window, you may see |
209 | failures in op/stat.t. Run "dmake test-notty" in that case. | |
210 | ||
a8deba26 | 211 | If you're using the Borland compiler, you may see a failure in op/taint.t |
3e3baf6d TB |
212 | arising from the inability to find the Borland Runtime DLLs on the system |
213 | default path. You will need to copy the DLLs reported by the messages | |
214 | from where Borland chose to install it, into the Windows system directory | |
215 | (usually somewhere like C:\WINNT\SYSTEM32), and rerun the test. | |
216 | ||
217 | Please report any other failures as described under L<BUGS AND CAVEATS>. | |
68dc0745 | 218 | |
137443ea | 219 | =head2 Installation |
220 | ||
9036c72f | 221 | Type "dmake install" (or "nmake install"). This will put the newly |
26618a56 GS |
222 | built perl and the libraries under whatever C<INST_TOP> points to in the |
223 | Makefile. It will also install the pod documentation under | |
9036c72f GS |
224 | C<$INST_TOP\$VERSION\lib\pod> and HTML versions of the same under |
225 | C<$INST_TOP\$VERSION\lib\pod\html>. To use the Perl you just installed, | |
226 | you will need to add two components to your PATH environment variable, | |
227 | C<$INST_TOP\$VERSION\bin>, and C<$INST_TOP\$VERSION\bin\$ARCHNAME>. | |
228 | For example: | |
229 | ||
63f87e49 | 230 | set PATH c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH% |
9036c72f | 231 | |
63f87e49 GS |
232 | If you opt to comment out INST_VER and INST_ARCH in the makefiles, the |
233 | installation structure is much simpler. In that case, it will be | |
234 | sufficient to add a single entry to the path, for instance: | |
235 | ||
236 | set PATH c:\perl\bin;%PATH% | |
137443ea | 237 | |
7bac28a0 | 238 | =head2 Usage Hints |
239 | ||
240 | =over 4 | |
241 | ||
242 | =item Environment Variables | |
243 | ||
244 | The installation paths that you set during the build get compiled | |
245 | into perl, so you don't have to do anything additional to start | |
246 | using that perl (except add its location to your PATH variable). | |
247 | ||
248 | If you put extensions in unusual places, you can set PERL5LIB | |
249 | to a list of paths separated by semicolons where you want perl | |
250 | to look for libraries. Look for descriptions of other environment | |
26618a56 GS |
251 | variables you can set in L<perlrun>. |
252 | ||
253 | You can also control the shell that perl uses to run system() and | |
254 | backtick commands via PERL5SHELL. See L<perlrun>. | |
7bac28a0 | 255 | |
9a40db4d GS |
256 | Perl does not depend on the registry, but it can look up certain default |
257 | values if you choose to put them there. Perl attempts to read entries from | |
258 | C<HKEY_CURRENT_USER\Software\Perl> and C<HKEY_LOCAL_MACHINE\Software\Perl>. | |
259 | Entries in the former override entries in the latter. One or more of the | |
260 | following entries (of type REG_SZ or REG_EXPAND_SZ) may be set: | |
261 | ||
4ea817c6 GS |
262 | lib-$] version-specific standard library path to add to @INC |
263 | lib standard library path to add to @INC | |
264 | sitelib-$] version-specific site library path to add to @INC | |
265 | sitelib site library path to add to @INC | |
266 | vendorlib-$] version-specific vendor library path to add to @INC | |
267 | vendorlib vendor library path to add to @INC | |
9a40db4d GS |
268 | PERL* fallback for all %ENV lookups that begin with "PERL" |
269 | ||
270 | Note the C<$]> in the above is not literal. Substitute whatever version | |
4ea817c6 | 271 | of perl you want to honor that entry, e.g. C<5.6.0>. Paths must be |
9a40db4d | 272 | separated with semicolons, as usual on win32. |
7bac28a0 | 273 | |
3e3baf6d TB |
274 | =item File Globbing |
275 | ||
63f87e49 GS |
276 | By default, perl handles file globbing using the File::Glob extension, |
277 | which provides portable globbing. | |
278 | ||
279 | If you want perl to use globbing that emulates the quirks of DOS | |
280 | filename conventions, you might want to consider using File::DosGlob | |
281 | to override the internal glob() implementation. See L<File::DosGlob> for | |
dfb634a9 | 282 | details. |
3e3baf6d | 283 | |
7bac28a0 | 284 | =item Using perl from the command line |
285 | ||
286 | If you are accustomed to using perl from various command-line | |
287 | shells found in UNIX environments, you will be less than pleased | |
63f87e49 | 288 | with what Windows offers by way of a command shell. |
7bac28a0 | 289 | |
290 | The crucial thing to understand about the "cmd" shell (which is | |
291 | the default on Windows NT) is that it does not do any wildcard | |
292 | expansions of command-line arguments (so wildcards need not be | |
293 | quoted). It also provides only rudimentary quoting. The only | |
294 | (useful) quote character is the double quote ("). It can be used to | |
295 | protect spaces in arguments and other special characters. The | |
296 | Windows NT documentation has almost no description of how the | |
297 | quoting rules are implemented, but here are some general observations | |
298 | based on experiments: The shell breaks arguments at spaces and | |
299 | passes them to programs in argc/argv. Doublequotes can be used | |
300 | to prevent arguments with spaces in them from being split up. | |
301 | You can put a double quote in an argument by escaping it with | |
302 | a backslash and enclosing the whole argument within double quotes. | |
303 | The backslash and the pair of double quotes surrounding the | |
304 | argument will be stripped by the shell. | |
305 | ||
306 | The file redirection characters "<", ">", and "|" cannot be quoted | |
307 | by double quotes (there are probably more such). Single quotes | |
308 | will protect those three file redirection characters, but the | |
309 | single quotes don't get stripped by the shell (just to make this | |
310 | type of quoting completely useless). The caret "^" has also | |
311 | been observed to behave as a quoting character (and doesn't get | |
312 | stripped by the shell also). | |
313 | ||
314 | Here are some examples of usage of the "cmd" shell: | |
315 | ||
316 | This prints two doublequotes: | |
317 | ||
318 | perl -e "print '\"\"' " | |
319 | ||
320 | This does the same: | |
321 | ||
322 | perl -e "print \"\\\"\\\"\" " | |
323 | ||
324 | This prints "bar" and writes "foo" to the file "blurch": | |
325 | ||
326 | perl -e "print 'foo'; print STDERR 'bar'" > blurch | |
327 | ||
328 | This prints "foo" ("bar" disappears into nowhereland): | |
329 | ||
330 | perl -e "print 'foo'; print STDERR 'bar'" 2> nul | |
331 | ||
332 | This prints "bar" and writes "foo" into the file "blurch": | |
333 | ||
334 | perl -e "print 'foo'; print STDERR 'bar'" 1> blurch | |
335 | ||
7bac28a0 | 336 | This pipes "foo" to the "less" pager and prints "bar" on the console: |
337 | ||
338 | perl -e "print 'foo'; print STDERR 'bar'" | less | |
339 | ||
340 | This pipes "foo\nbar\n" to the less pager: | |
341 | ||
7bac28a0 | 342 | perl -le "print 'foo'; print STDERR 'bar'" 2>&1 | less |
343 | ||
344 | This pipes "foo" to the pager and writes "bar" in the file "blurch": | |
345 | ||
346 | perl -e "print 'foo'; print STDERR 'bar'" 2> blurch | less | |
347 | ||
348 | ||
63f87e49 | 349 | Discovering the usefulness of the "command.com" shell on Windows 9x |
7bac28a0 | 350 | is left as an exercise to the reader :) |
351 | ||
352 | =item Building Extensions | |
353 | ||
354 | The Comprehensive Perl Archive Network (CPAN) offers a wealth | |
355 | of extensions, some of which require a C compiler to build. | |
63f87e49 GS |
356 | Look in http://www.cpan.org/ for more information on CPAN. |
357 | ||
358 | Note that not all of the extensions available from CPAN may work | |
359 | in the Win32 environment; you should check the information at | |
360 | http://testers.cpan.org/ before investing too much effort into | |
361 | porting modules that don't readily build. | |
7bac28a0 | 362 | |
363 | Most extensions (whether they require a C compiler or not) can | |
364 | be built, tested and installed with the standard mantra: | |
365 | ||
366 | perl Makefile.PL | |
3e3baf6d TB |
367 | $MAKE |
368 | $MAKE test | |
369 | $MAKE install | |
7bac28a0 | 370 | |
ee4d903c GS |
371 | where $MAKE is whatever 'make' program you have configured perl to |
372 | use. Use "perl -V:make" to find out what this is. Some extensions | |
373 | may not provide a testsuite (so "$MAKE test" may not do anything, or | |
374 | fail), but most serious ones do. | |
375 | ||
376 | It is important that you use a supported 'make' program, and | |
377 | ensure Config.pm knows about it. If you don't have nmake, you can | |
378 | either get dmake from the location mentioned earlier, or get an | |
379 | old version of nmake reportedly available from: | |
380 | ||
381 | ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe | |
382 | ||
383 | Another option is to use the make written in Perl, available from | |
384 | CPAN: | |
385 | ||
63f87e49 | 386 | http://www.cpan.org/authors/id/NI-S/Make-0.03.tar.gz |
ee4d903c | 387 | |
63f87e49 | 388 | You may also use dmake. See L</"Make"> above on how to get it. |
4ea817c6 | 389 | |
ee4d903c GS |
390 | Note that MakeMaker actually emits makefiles with different syntax |
391 | depending on what 'make' it thinks you are using. Therefore, it is | |
392 | important that one of the following values appears in Config.pm: | |
393 | ||
394 | make='nmake' # MakeMaker emits nmake syntax | |
395 | make='dmake' # MakeMaker emits dmake syntax | |
396 | any other value # MakeMaker emits generic make syntax | |
397 | (e.g GNU make, or Perl make) | |
398 | ||
399 | If the value doesn't match the 'make' program you want to use, | |
400 | edit Config.pm to fix it. | |
7bac28a0 | 401 | |
3e3baf6d TB |
402 | If a module implements XSUBs, you will need one of the supported |
403 | C compilers. You must make sure you have set up the environment for | |
404 | the compiler for command-line compilation. | |
7bac28a0 | 405 | |
3e3baf6d | 406 | If a module does not build for some reason, look carefully for |
7bac28a0 | 407 | why it failed, and report problems to the module author. If |
408 | it looks like the extension building support is at fault, report | |
409 | that with full details of how the build failed using the perlbug | |
410 | utility. | |
411 | ||
9cde0e7f GS |
412 | =item Command-line Wildcard Expansion |
413 | ||
414 | The default command shells on DOS descendant operating systems (such | |
415 | as they are) usually do not expand wildcard arguments supplied to | |
416 | programs. They consider it the application's job to handle that. | |
417 | This is commonly achieved by linking the application (in our case, | |
418 | perl) with startup code that the C runtime libraries usually provide. | |
419 | However, doing that results in incompatible perl versions (since the | |
420 | behavior of the argv expansion code differs depending on the | |
421 | compiler, and it is even buggy on some compilers). Besides, it may | |
422 | be a source of frustration if you use such a perl binary with an | |
423 | alternate shell that *does* expand wildcards. | |
424 | ||
425 | Instead, the following solution works rather well. The nice things | |
426 | about it: 1) you can start using it right away 2) it is more powerful, | |
427 | because it will do the right thing with a pattern like */*/*.c | |
428 | 3) you can decide whether you do/don't want to use it 4) you can | |
429 | extend the method to add any customizations (or even entirely | |
430 | different kinds of wildcard expansion). | |
431 | ||
432 | C:\> copy con c:\perl\lib\Wild.pm | |
433 | # Wild.pm - emulate shell @ARGV expansion on shells that don't | |
434 | use File::DosGlob; | |
435 | @ARGV = map { | |
436 | my @g = File::DosGlob::glob($_) if /[*?]/; | |
437 | @g ? @g : $_; | |
438 | } @ARGV; | |
439 | 1; | |
440 | ^Z | |
441 | C:\> set PERL5OPT=-MWild | |
442 | C:\> perl -le "for (@ARGV) { print }" */*/perl*.c | |
443 | p4view/perl/perl.c | |
444 | p4view/perl/perlio.c | |
445 | p4view/perl/perly.c | |
446 | perl5.005/win32/perlglob.c | |
447 | perl5.005/win32/perllib.c | |
448 | perl5.005/win32/perlglob.c | |
449 | perl5.005/win32/perllib.c | |
450 | perl5.005/win32/perlglob.c | |
451 | perl5.005/win32/perllib.c | |
452 | ||
453 | Note there are two distinct steps there: 1) You'll have to create | |
454 | Wild.pm and put it in your perl lib directory. 2) You'll need to | |
455 | set the PERL5OPT environment variable. If you want argv expansion | |
456 | to be the default, just set PERL5OPT in your default startup | |
457 | environment. | |
458 | ||
459 | If you are using the Visual C compiler, you can get the C runtime's | |
460 | command line wildcard expansion built into perl binary. The resulting | |
461 | binary will always expand unquoted command lines, which may not be | |
462 | what you want if you use a shell that does that for you. The expansion | |
463 | done is also somewhat less powerful than the approach suggested above. | |
464 | ||
c90c0ff4 | 465 | =item Win32 Specific Extensions |
466 | ||
467 | A number of extensions specific to the Win32 platform are available | |
468 | from CPAN. You may find that many of these extensions are meant to | |
469 | be used under the Activeware port of Perl, which used to be the only | |
470 | native port for the Win32 platform. Since the Activeware port does not | |
471 | have adequate support for Perl's extension building tools, these | |
472 | extensions typically do not support those tools either, and therefore | |
473 | cannot be built using the generic steps shown in the previous section. | |
474 | ||
475 | To ensure smooth transitioning of existing code that uses the | |
9036c72f GS |
476 | ActiveState port, there is a bundle of Win32 extensions that contains |
477 | all of the ActiveState extensions and most other Win32 extensions from | |
c90c0ff4 | 478 | CPAN in source form, along with many added bugfixes, and with MakeMaker |
479 | support. This bundle is available at: | |
480 | ||
63f87e49 | 481 | http://www.cpan.org/authors/id/GSAR/libwin32-0.151.zip |
c90c0ff4 | 482 | |
483 | See the README in that distribution for building and installation | |
484 | instructions. Look for later versions that may be available at the | |
485 | same location. | |
486 | ||
156a3eb7 GS |
487 | =item Running Perl Scripts |
488 | ||
489 | Perl scripts on UNIX use the "#!" (a.k.a "shebang") line to | |
490 | indicate to the OS that it should execute the file using perl. | |
491 | Win32 has no comparable means to indicate arbitrary files are | |
492 | executables. | |
493 | ||
494 | Instead, all available methods to execute plain text files on | |
495 | Win32 rely on the file "extension". There are three methods | |
496 | to use this to execute perl scripts: | |
497 | ||
498 | =over 8 | |
499 | ||
500 | =item 1 | |
501 | ||
502 | There is a facility called "file extension associations" that will | |
503 | work in Windows NT 4.0. This can be manipulated via the two | |
504 | commands "assoc" and "ftype" that come standard with Windows NT | |
505 | 4.0. Type "ftype /?" for a complete example of how to set this | |
506 | up for perl scripts (Say what? You thought Windows NT wasn't | |
507 | perl-ready? :). | |
508 | ||
509 | =item 2 | |
510 | ||
511 | Since file associations don't work everywhere, and there are | |
512 | reportedly bugs with file associations where it does work, the | |
513 | old method of wrapping the perl script to make it look like a | |
514 | regular batch file to the OS, may be used. The install process | |
515 | makes available the "pl2bat.bat" script which can be used to wrap | |
516 | perl scripts into batch files. For example: | |
517 | ||
518 | pl2bat foo.pl | |
519 | ||
520 | will create the file "FOO.BAT". Note "pl2bat" strips any | |
521 | .pl suffix and adds a .bat suffix to the generated file. | |
522 | ||
523 | If you use the 4DOS/NT or similar command shell, note that | |
524 | "pl2bat" uses the "%*" variable in the generated batch file to | |
525 | refer to all the command line arguments, so you may need to make | |
526 | sure that construct works in batch files. As of this writing, | |
527 | 4DOS/NT users will need a "ParameterChar = *" statement in their | |
528 | 4NT.INI file, or will need to execute "setdos /p*" in the 4DOS/NT | |
529 | startup file to enable this to work. | |
530 | ||
531 | =item 3 | |
532 | ||
533 | Using "pl2bat" has a few problems: the file name gets changed, | |
534 | so scripts that rely on C<$0> to find what they must do may not | |
535 | run properly; running "pl2bat" replicates the contents of the | |
536 | original script, and so this process can be maintenance intensive | |
537 | if the originals get updated often. A different approach that | |
538 | avoids both problems is possible. | |
539 | ||
540 | A script called "runperl.bat" is available that can be copied | |
541 | to any filename (along with the .bat suffix). For example, | |
542 | if you call it "foo.bat", it will run the file "foo" when it is | |
543 | executed. Since you can run batch files on Win32 platforms simply | |
544 | by typing the name (without the extension), this effectively | |
545 | runs the file "foo", when you type either "foo" or "foo.bat". | |
546 | With this method, "foo.bat" can even be in a different location | |
547 | than the file "foo", as long as "foo" is available somewhere on | |
548 | the PATH. If your scripts are on a filesystem that allows symbolic | |
549 | links, you can even avoid copying "runperl.bat". | |
550 | ||
551 | Here's a diversion: copy "runperl.bat" to "runperl", and type | |
552 | "runperl". Explain the observed behavior, or lack thereof. :) | |
553 | Hint: .gnidnats llits er'uoy fi ,"lrepnur" eteled :tniH | |
554 | ||
555 | =back | |
556 | ||
7bac28a0 | 557 | =item Miscellaneous Things |
558 | ||
559 | A full set of HTML documentation is installed, so you should be | |
560 | able to use it if you have a web browser installed on your | |
561 | system. | |
562 | ||
563 | C<perldoc> is also a useful tool for browsing information contained | |
564 | in the documentation, especially in conjunction with a pager | |
565 | like C<less> (recent versions of which have Win32 support). You may | |
566 | have to set the PAGER environment variable to use a specific pager. | |
567 | "perldoc -f foo" will print information about the perl operator | |
568 | "foo". | |
569 | ||
570 | If you find bugs in perl, you can run C<perlbug> to create a | |
571 | bug report (you may have to send it manually if C<perlbug> cannot | |
572 | find a mailer on your system). | |
573 | ||
574 | =back | |
575 | ||
68dc0745 | 576 | =head1 BUGS AND CAVEATS |
577 | ||
63f87e49 GS |
578 | Some of the built-in functions do not act exactly as documented in |
579 | L<perlfunc>, and a few are not implemented at all. To avoid | |
580 | surprises, particularly if you have had prior exposure to Perl | |
581 | in other operating environments or if you intend to write code | |
582 | that will be portable to other environments, see L<perlport> | |
583 | for a reasonably definitive list of these differences. | |
6890e559 | 584 | |
63f87e49 GS |
585 | Not all extensions available from CPAN may build or work properly |
586 | in the Win32 environment. See L</"Building Extensions">. | |
68dc0745 | 587 | |
63f87e49 GS |
588 | Most C<socket()> related calls are supported, but they may not |
589 | behave as on Unix platforms. See L<perlport> for the full list. | |
68dc0745 | 590 | |
3e3baf6d | 591 | Signal handling may not behave as on Unix platforms (where it |
f7c603cb GS |
592 | doesn't exactly "behave", either :). For instance, calling C<die()> |
593 | or C<exit()> from signal handlers will cause an exception, since most | |
594 | implementations of C<signal()> on Win32 are severely crippled. | |
595 | Thus, signals may work only for simple things like setting a flag | |
596 | variable in the handler. Using signals under this port should | |
597 | currently be considered unsupported. | |
68dc0745 | 598 | |
68dc0745 | 599 | Please send detailed descriptions of any problems and solutions that |
600 | you may find to <F<perlbug@perl.com>>, along with the output produced | |
601 | by C<perl -V>. | |
602 | ||
603 | =head1 AUTHORS | |
604 | ||
605 | =over 4 | |
606 | ||
3e3baf6d | 607 | Gary Ng E<lt>71564.1743@CompuServe.COME<gt> |
68dc0745 | 608 | |
6e238990 | 609 | Gurusamy Sarathy E<lt>gsar@activestate.comE<gt> |
68dc0745 | 610 | |
3e3baf6d | 611 | Nick Ing-Simmons E<lt>nick@ni-s.u-net.comE<gt> |
68dc0745 | 612 | |
613 | =back | |
614 | ||
f7c603cb GS |
615 | This document is maintained by Gurusamy Sarathy. |
616 | ||
68dc0745 | 617 | =head1 SEE ALSO |
618 | ||
619 | L<perl> | |
620 | ||
621 | =head1 HISTORY | |
622 | ||
623 | This port was originally contributed by Gary Ng around 5.003_24, | |
624 | and borrowed from the Hip Communications port that was available | |
5db10396 GS |
625 | at the time. Various people have made numerous and sundry hacks |
626 | since then. | |
68dc0745 | 627 | |
3e3baf6d TB |
628 | Borland support was added in 5.004_01 (Gurusamy Sarathy). |
629 | ||
9a40db4d GS |
630 | GCC/mingw32 support was added in 5.005 (Nick Ing-Simmons). |
631 | ||
80252599 GS |
632 | Support for PERL_OBJECT was added in 5.005 (ActiveState Tool Corp). |
633 | ||
5db10396 | 634 | Support for fork() emulation was added in 5.6 (ActiveState Tool Corp). |
68dc0745 | 635 | |
5db10396 GS |
636 | Win9x support was added in 5.6 (Benjamin Stuhl). |
637 | ||
807d88e1 | 638 | Last updated: 22 March 2000 |
3e3baf6d | 639 | |
5db10396 | 640 | =cut |