The last of these is a high quality freeware compiler. Use version
3.2.x or later for the best results with this compiler.
-The Microsoft Visual C++ compiler is also now being given away free in
-the "Visual C++ Toolkit 2003", and also as part of the ".NET Framework
-SDK". This is the same compiler that ships with "Visual Studio .NET 2003
-Professional".
+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", and also as part of the ".NET Framework SDK", and
+is the same compiler that ships with "Visual Studio .NET 2003 Professional".
This port can also be built on the Intel IA64 using:
A port of dmake for Windows is available from:
- http://www.cpan.org/authors/id/GSAR/dmake-4.1pl1-win32.zip
+ http://search.cpan.org/dist/dmake/
-(This is a fixed version of the original dmake sources obtained from
-http://www.wticorp.com/ As of version 4.1PL1, the original
-sources did not build as shipped and had various other problems.
-A patch is included in the above fixed version.)
-
-Fetch and install dmake somewhere on your path (follow the instructions
-in the README.NOW file).
+Fetch and install dmake somewhere on your path.
There exists a minor coexistence problem with dmake and Borland C++
compilers. Namely, if a distribution has C files named with mixed
=item MinGW release 3 with gcc
-The latest release of MinGW at the time of writing is 3.1.0, which contains
+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/
=item *
-Edit the makefile.mk (or Makefile, if you're using nmake) and change
+Edit the makefile.mk (or Makefile, if you're using nmake) and change
the values of INST_DRV and INST_TOP. You can also enable various
build flags. These are explained in the makefiles.
may end up building against the installed perl's lib/CORE directory rather
than the one being tested.
-You will have to make sure that CCTYPE is set correctly and that
+You will have to make sure that CCTYPE is set correctly and that
CCHOME points to wherever you installed your compiler.
The default value for CCHOME in the makefiles for Visual C++
may not be correct for some versions. Make sure the default exists
and is valid.
+You may also need to comment out a line C<DELAYLOAD = ...> in the
+makefile, in case you're using an older version of the Visual C++ compiler
+(e.g. 6.0 without service packs) and if the linker reports an internal
+error.
+
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
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.
+
Be sure to read the instructions near the top of the makefiles carefully.
=item *
alternate shell that *does* expand wildcards.
Instead, the following solution works rather well. The nice things
-about it are 1) you can start using it right away; 2) it is more
+about it are 1) you can start using it right away; 2) it is more
powerful, because it will do the right thing with a pattern like
*/*/*.c; 3) you can decide whether you do/don't want to use it; and
-4) you can extend the method to add any customizations (or even
+4) you can extend the method to add any customizations (or even
entirely different kinds of wildcard expansion).
C:\> copy con c:\perl\lib\Wild.pm
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. This bundle is available at:
+support. The latest version of this bundle is available at:
- http://www.cpan.org/modules/by-module/Win32/libwin32-0.191.zip
+ http://search.cpan.org/dist/libwin32/
See the README in that distribution for building and installation
-instructions. Look for later versions that may be available at the
-same location.
+instructions.
=item Notes on 64-bit Windows
=head1 BUGS AND CAVEATS
-Norton AntiVirus interferes with the build process, particularly if
-set to "AutoProtect, All Files, when Opened". Unlike large applications
-the perl build process opens and modifies a lot of files. Having the
+Norton AntiVirus interferes with the build process, particularly if
+set to "AutoProtect, All Files, when Opened". Unlike large applications
+the perl build process opens and modifies a lot of files. Having the
the AntiVirus scan each and every one slows build the process significantly.
Worse, with PERLIO=stdio the build process fails with peculiar messages
-as the virus checker interacts badly with miniperl.exe writing configure
+as the virus checker interacts badly with miniperl.exe writing configure
files (it seems to either catch file part written and treat it as suspicious,
or virus checker may have it "locked" in a way which inhibits miniperl
-updating it). The build does complete with
+updating it). The build does complete with
set PERLIO=perlio
variable in the handler. Using signals under this port should
currently be considered unsupported.
-Please send detailed descriptions of any problems and solutions that
+Please send detailed descriptions of any problems and solutions that
you may find to E<lt>F<perlbug@perl.org>E<gt>, along with the output
produced by C<perl -V>.
Support for 64-bit Windows added in 5.8 (ActiveState Corp).
-Last updated: 15 February 2005
+Last updated: 16 June 2005
=cut
https://perl5.git.perl.org / perl5.git / blobdiff