README.win32 - Parrot under Windows
These are instructions for building the "native" port of Parrot under Windows 2000/XP on the Intel x86 architecture.
Win32 "native" ports require no additional software to run but the operating system. There should be other READMEs for (emulation) systems that run on Win32, eg Cygwin.
Native compilers include:
Borland C++ (bcc) version xxx or later Microsoft Visual C++ (cl) version 13.10.3077 or later MinGW32 with GCC (gcc) version 3.4.2 or later Intel C++ (icl) version 8.0.48 works
Setting Up Parrot
You need "nmake" to build Parrot under Windows with Microsoft compilers. It should be available via Microsoft Visual Studio .NET 2003 or the Microsoft .NET Framework SDK 1.1. Download the latter from the Microsoft .NET Framework Homepage http://msdn.microsoft.com/netframework/.
Note: Parrot will not build using nmake v1.5 from the MS web site. Download one of the above toolkits to obtain a later version, either v7 or v8.
MinGW works with its GNU "make" (v 3.81) port and its name is 'mingw32-make.exe'. If you also have the Minimal SYStem (MSYS) installed, you will need to remove the Msys/bin folder from your PATH environment variable before calling "perl Configure.pl" and mingw32-make. Perl detects and calls /bin/sh.exe, if found, whenever shelling a new process. sh.exe causes problems for mingw32-make.exe because of its inability to handle Windows pathnames with backslashes. You must run "perl Configure.pl" and mingw32-make from a dosbox; running those commands from an MSYS shell window will experience the same backslash path problems.
- Command Shell
The surest way to build it is on Windows NT/2000/XP, using the cmd shell.
Parrot no longer comes with its own ICU, thus you need to install it on your system if you want to use it. Note that ICU is now optional, you can build Parrot without it, by not installing it or asking Parrot to ignore it (
If you want to use ICU, download it from http://www.icu-project.org/download/.
If you want to use precompiled binaries, do the following. Download the package matching your compiler, unpack it (say, into C:\usr\lib), add the bin directory to
PATH, and tell Configure.pl to use it.
mkdir C:\usr\lib unzip icu4c-4_0-Win32-msvc8.zip -d C:\usr\lib mkdir C:\usr\lib\data set PATH=%PATH%;C:\usr\lib\icu\bin cd <parrot directory> perl Configure.pl --icushared="C:\usr\lib\icu\lib\icudt.lib C:\usr\lib\icu\lib\icuuc.lib" --icuheaders="C:\usr\lib\icu\include"
Note the step of creating the C:\usr\lib\data directory, as Parrot really wants it and the binary packages don't contain it. It doesn't need to contain anything though, as the data is pulled in from lib/icudt.lib, which contains the standard data in binary form.
- Optional libraries
The availability of these libraries is checked by Configure.pl.
libcrypto - a part of libssl http://www.openssl.org/
gettext - library and tools for native language support http://gnuwin32.sourceforge.net/
gdbm - GNU database manager http://gnuwin32.sourceforge.net/
GMP - GNU multiple precision arithmetic library http://developer.berlios.de/projects/win32gmp/
pcre - Perl-Compatible Regular Expression library http://gnuwin32.sourceforge.net/
readline - edit command lines http://gnuwin32.sourceforge.net/
- Optional utilities
The availability of these utilities is checked by Configure.pl or by some test.
antlr - ANother Tool for Language Recognition http://www.antlr.org/
m4 - macro language processor http://gnuwin32.sourceforge.net/
SVN::Client - Perl wrapper of Subversion client functions http://subversion.tigris.org/ (svn-win32-1.4.x_pl.zip)
- Inno Setup
Inno Setup is a free installer for Windows programs.
The latest release of Inno Setup at the time of writing is 5.2.3.
The HomePage is on http://www.jrsoftware.org/.
Add the directory to PATH.
set PATH=%PATH%;C:\Program Files\Inno Setup 5
- Borland C++
- Microsoft Visual C++
Since mid April 2004, Visual C++ comes in two flavors. Microsoft Visual Studio .NET 2003 (http://msdn.microsoft.com/visualc/), which includes the full blown IDE, and Microsoft Visual C++ Toolkit 2003 (http://msdn.microsoft.com/visualc/vctoolkit2003/), which is a free (but unsupported) package, containing only the basic compiler and linker stuff.
If you use the Toolkit, be sure to follow the directions for setting up your build environment that come with the perl distributions. (README.win32 in the latest perl distribution.) You may have to substitute "Microsoft Platform SDK" wherever "Microsoft SDK" is listed, depending on the your install. You can ignore the entries regarding "win32/config.vc", but be sure to create the "link.bat" batch file. Copy the missing files mentioned, run the Toolkit Command Prompt, set the appropriate env vars, and you should be fine. (For env vars, you can update them under My Computer-> properties so they are available whenever you open a shell.)
Note: It is possible to use ActiveState Perl with the Toolkit: you don't have to compile your own perl.
- Strawberry Perl
With the Strawberry perl distro from http://strawberryperl.com/, gcc is included. To build parrot, use the strawberry perl binary to run Configure.pl, and then follow the directions.
- MinGW32 with GCC
The latest release of MinGW package at the time of writing is 5.1.3, which contains gcc-3.4.5 as current release. It can be downloaded here: http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe
The HomePage is on http://www.mingw.org/.
With the ActiveState Perl distribution, tell Configure.pl to use gcc :
perl Configure.pl --cc=gcc --icushared="C:\usr\lib\icu\lib\icudt.lib C:\usr\lib\icu\lib\icuuc.lib" --icuheaders="C:\usr\lib\icu\include" or perl Configure.pl --cc=gcc --without-icu
- Intel C++
This command creates a setup-parrot-x.y.z.exe that contains all parrot install directories.
BUGS AND CAVEATS
Threads, Events, and Signals are missing.
- Ron Blaschke <firstname.lastname@example.org>
- François Perrad <email@example.com>
This document is maintained by The Parrot Developers (<firstname.lastname@example.org>).
This document borrows heavily from Perl's README.win32.
GCC/mingw32 support was added in 0.1.2 (François Perrad).
Last updated: 22 July 2008
Hey! The above document had some coding errors, which are explained below:
- Around line 232:
Non-ASCII character seen before =encoding in 'François'. Assuming UTF-8