r5 - 29 Jul 2006 - JoenioCosta

BUGS AND CAVEATS
ACKNOWLEDGEMENTS
AUTHORS
SEE ALSO
HISTORY
TRADUZINDO

OBSERVAÇÃO

Se você está lendo este arquivo em seu formato original, ignore quaisquer caracteres estranhos. Ele é escrito no formato POD (ver: pod/perlpod.pod) que é especialmente desenvolvido para leitura sem formatação.

voltar para o topo

NOME

perlwin32 - Perl em ambiente Windows

voltar para o topo

SINOPSE

Estas são instruções para compilação Perl em ambiente Windows 9x/NT/2000/XP em arquiteturas Intel x86 e Itanium.

voltar para o topo

DESCRIÇÃO

Antes de começar, você deve dar uma lida no arquivo README localizado no diretório raiz onde esta distribuição Perl foi descompactada. Certifique-se de que você tenha lido e entendido os termos sob os quais este software está sendo distribuído. Além disso, certifique-se de você tenha lido BUGS E AVISOS abaixo para ter conhecimento das limitações desta versão. O arquivo INSTALL que se encontra no diretório raiz contém muita informação que é relevante apenas para pessoas que estão compilando Perl em sistemas Unix. Você pode tranquilamente ignorar qualquer informação que mencione ``Configure''. Você pode querer conferir outras duas opções para compilar uma perl de forma à funcionar no Windows NT: os arquivos README.cygwin e README.os2, definem conjuntos de regras para compilar uma perl que funcionará em plataformas Win32. Estes dois métodos provavelmente permitirão que você compile uma perl mais compatível com sistemas Unix, mas você precisará baixar e utilizar diversos outros softwares tanto para a fase de compilação quanto de execução que são descritos nestes arquivos. Este conjunto de instruções detina-se à descrever uma distribuição ``nativa'' de Perl para plataformas Win32. Isto incluí as versões de Sistemas Operacionais Windows de 32 e 64 bits. A instalação Perl resultante não requer nenhum software adicional para rodar (além dos já incluídos no seu sistema operacional). Atualmente esta distribuição é capaz de utilizar um dos seguintes compiladores na arquitetura Intel x86:

      Borland C++           versão 5.02 ou posterior

      Microsoft Visual C++  versão 4.2 ou posterior

      MinGW com gcc        gcc versão 2.95.2 ou posterior

Sendo este último um compilador freeware de alta qualidade. Use a versão 3.2.x ou posterior para melhores resultados com este compilador. O compilador Microsoft Visual C++ também é conhecido por ser distribuído gratuitamente com o ``Visual C++ Toolkit 2003'' a também é parte do ``.NET Framework SDK``. Este é o mesmo compilador que é distribuído com o ``Visual Studio .NET 2003 Professional''. Esta distribuição também pode ser compilada em Intel IA64 usando:

      Microsoft Platform SDK    Nov 2001 (compilador e ferramentas 64-bit)

A Plataforma MS SDK pode ser baixada em http://www.microsoft.com/. Esta distribuição suporta com perfeição o MakeMaker? (o conjunto de módulos usado para compilar extensões para perl). Sendo assim, você deve ser capaz de compilar e instalar a maioria das extensões encontradas nos sites CPAN. Veja Dicas de Uso para Perl em Win32 abaixo para dicas gerais sobre isto.

Configurando Perl em Win32

Make

Você precisa de um programa ``make'' para compilar os códigos-fonte. Se você

está usando Visual C++ ou as ferramentas da plataforma SDK em ambiente

Windows NT/2000/XP, o nmake irá funcionar. Outras distribuições precisarão

do dmake.

dmake é um programa make disponível de forma gratuita que possui

dmake is a freely available make that has very nice macro features

and parallelability.

Uma distribuição dmake para Windows está disponível em:

    http://search.cpan.org/dist/dmake/

Baixe e instale o dmake em algum diretório que faça parte do seu path.

Existem pequenos problemas de co-existência entre o dmake e compiladores

Borland C++. Especificamente, se uma distribuição possui arquivos C nomeados

com uma mistura de caixa alta e baixa, eles serão compilados nos arquivos-obj

apropriados com todas as letras de seu nome em caixa baixa, e toda a vez que

o dmake for chamado para atualizar os arquivos, ele tentará recompilar estes

arquivos novamente. Por exemplo, a distribuição Tk tem muitos arquivos destes,

resultando em em recompilações sem sentido cada vez que o dmake for chamado.

Para evitar isto, você pode utilizar o script ``sync_ext.pl'' depois de compilar uma

distribuição com sucesso. Ele está disponível no sub-diretório win32 do

código-fonte da distribuição Perl.

Shell de Comandos

    Use o shell padrão "cmd" que acompanha o NT. Algumas versões do popular shell 4DOS/NET têm incompatibilidades que podem causar problemas. Se a compilação falhar com este shell, tente recompilar com o shell cmd.

    O Makefile nmake também possui incompatibilidades conhecidas com o shell "command.com" que acompanha o Windows 9x. Você terá que usar dmake e makefile.mk para compilar em Windows9x.

    A maneira mais certa para compilar é usando o shell cmd em Windows NT/2000/XP.

    Certifique-se que o caminho para o diretório de compilação não contenha espaços. A compilação normalmente funciona nestas circunstâncias, mas alguns testes falharão.

Borland C++

Se você está usando o compilador Borland, você precisará do dmake. (O make fornecido pela Borland não funcionará para compilações MakeMaker? ).

Veja Make acima.

Microsoft Visual C++

The nmake that comes with Visual C++ will suffice for building.

You will need to run the VCVARS32.BAT file, usually found somewhere

like C:\MSDEV4.2\BIN or C:\Program Files\Microsoft Visual Studio\VC98\Bin.

This will set your build environment.

You can also use dmake to build using Visual C++; provided, however,

you set OSRELEASE to ``microsft'' (or whatever the directory name

under which the Visual C dmake configuration lives) in your environment

and edit win32/config.vc to change ``make=nmake'' into ``make=dmake''. The

latter step is only essential if you want to use dmake as your default

make for building extensions using MakeMaker? .

Microsoft Visual C++ Toolkit 2003

This free toolkit contains the same compiler and linker that ship with

Visual Studio .NET 2003 Professional, but doesn't contain everything

necessary to build Perl.

You will also need to download the ``Platform SDK'' (the ``Core SDK'' and ``MDAC

SDK`` components are required) for header files, libraries and rc.exe, and

``.NET Framework SDK'' for more libraries and nmake.exe. Note that the latter

(which also includes the free compiler and linker) requires the ``.NET

Framework Redistributable`` to be installed first. This can be downloaded and

installed separately, but is included in the ``Visual C++ Toolkit 2003'' anyway.

These packages can all be downloaded by searching in the Download Center at

http://www.microsoft.com/downloads/search.aspx?displaylang=en

The Platform SDK packages can also be obtained from the Platform SDK Update

site: http://www.microsoft.com/msdownload/platformsdk/sdkupdate Note that this

site requires Internet Explorer 5.0 or later to function, but the site's home

page currently gives links to two download pages for users of other browsers:

For Windows XP Service Pack 2:

http://www.microsoft.com/msdownload/platformsdk/sdkupdate/XPSP2FULLInstall.htm

For Windows Server 2003:

http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm

According to the download pages the Toolkit and the .NET Framework SDK are only

supported on Windows 2000/XP/2003, so trying to use these tools on Windows

95/98/ME and even Windows NT probably won't work.

Install the Toolkit first, then the Platform SDK, then the .NET Framework SDK.

Setup your environment as follows (assuming default installation locations

were chosen):

        SET PATH=%SystemRoot%\system32;%SystemRoot%;C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;C:\Program Files\Microsoft SDK\Bin;C:\Program Files\Microsoft.NET\SDK\v1.1\Bin

        SET INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit 2003\include;C:\Program Files\Microsoft SDK\include;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include

        SET LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;C:\Program Files\Microsoft SDK\lib;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Several required files will still be missing:

        C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322

        ar='lib'

        ar='link /lib'

        @echo off

        link /lib %*

        cl.exe /c /I. /D_CRTBLD setargv.c

Microsoft Platform SDK 64-bit Compiler

The nmake that comes with the Platform SDK will suffice for building

Perl. Make sure you are building within one of the ``Build Environment''

shells available after you install the Platform SDK from the Start Menu.

MinGW release 3 with gcc

The latest release of MinGW? at the time of writing is 3.1.0, which contains

gcc-3.2.3. It can be downloaded here:

    http://www.mingw.org/

Perl also compiles with earlier releases of gcc (2.95.2 and up). See below

for notes about using earlier versions of MinGW? /gcc.

You also need dmake. See Make above on how to get it.

MinGW release 1 with gcc

The MinGW? -1.1 bundle contains gcc-2.95.3.

Make sure you install the binaries that work with MSVCRT.DLL as indicated

in the README for the GCC bundle. You may need to set up a few environment

variables (usually ran from a batch file).

There are a couple of problems with the version of gcc-2.95.2-msvcrt.exe

released 7 November 1999:

    http://downloads.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip

    ftp://ftp.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip

Building

MinGW?

ftp://ftp.funet.fi/pub/crypt/mirrors/dsi/libdes/,

crypt()

Testing Perl on Win32

Type ``dmake test'' (or ``nmake test''). This will run most of the tests from the testsuite (many tests will be skipped). There should be no test failures when running under Windows NT/2000/XP. Many tests will fail under Windows 9x due to the inferior command shell. Some test failures may occur if you use a command shell other than the native ``cmd.exe'', or if you are building from a path that contains spaces. So don't do that. If you are running the tests from a emacs shell window, you may see failures in op/stat.t. Run ``dmake test-notty'' in that case. If you're using the Borland compiler, you may see a failure in op/taint.t arising from the inability to find the Borland Runtime DLLs on the system default path. You will need to copy the DLLs reported by the messages from where Borland chose to install it, into the Windows system directory (usually somewhere like C:\WINNT\SYSTEM32) and rerun the test. If you're using Borland compiler versions 5.2 and below, you may run into problems finding the correct header files when building extensions. For example, building the ``Tk'' extension may fail because both perl and Tk contain a header file called ``patchlevel.h''. The latest Borland compiler (v5.5) is free of this misbehaviour, and it even supports an option -VI- for backward (bugward) compatibility for using the old Borland search algorithm to locate header files. If you run the tests on a FAT partition, you may see some failures for link() related tests:

    Failed Test                     Stat Wstat Total Fail  Failed  List

    ../ext/IO/lib/IO/t/io_dup.t                    6    4  66.67%  2-5

    ../lib/File/Temp/t/mktemp.t                    9    1  11.11%  2

    ../lib/File/Temp/t/posix.t                     7    1  14.29%  3

    ../lib/File/Temp/t/security.t                 13    1   7.69%  2

    ../lib/File/Temp/t/tempfile.t                 20    2  10.00%  2 4

    comp/multiline.t                               6    2  33.33%  5-6

    io/dup.t                                       8    6  75.00%  2-7

    op/write.t                                    47    7  14.89%  1-3 6 9-11

Testing on NTFS avoids these errors. Furthermore, you should make sure that during make test you do not have any GNU tool packages in your path: some toolkits like Unixutils include some tools (type for instance) which override the Windows ones and makes tests fail. Remove them from your path while testing to avoid these errors. Please report any other failures as described under BUGS AND CAVEATS.

Installation of Perl on Win32

Type ``dmake install'' (or ``nmake install''). This will put the newly built perl and the libraries under whatever INST_TOP points to in the Makefile. It will also install the pod documentation under $INST_TOP\$INST_VER\lib\pod and HTML versions of the same under $INST_TOP\$INST_VER\lib\pod\html. To use the Perl you just installed you will need to add a new entry to your PATH environment variable: $INST_TOP\bin, e.g.

    set PATH=c:\perl\bin;%PATH%

If you opted to uncomment INST_VER and INST_ARCH in the makefile then the installation structure is a little more complicated and you will need to add two new PATH components instead: $INST_TOP\$INST_VER\bin and $INST_TOP\$INST_VER\bin\$ARCHNAME, e.g.

    set PATH=c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH%

Usage Hints for Perl on Win32

Environment Variables

The installation paths that you set during the build get compiled

into perl, so you don't have to do anything additional to start

using that perl (except add its location to your PATH variable).

If you put extensions in unusual places, you can set PERL5LIB?

to a list of paths separated by semicolons where you want perl

to look for libraries. Look for descriptions of other environment

variables you can set in the perlrun manpage.

You can also control the shell that perl uses to run system() and

backtick commands via PERL5SHELL? . See the perlrun manpage.

Perl does not depend on the registry, but it can look up certain default

values if you choose to put them there. Perl attempts to read entries from

HKEY_CURRENT_USER\Software\Perl and HKEY_LOCAL_MACHINE\Software\Perl.

Entries in the former override entries in the latter. One or more of the

following entries (of type REG_SZ or REG_EXPAND_SZ) may be set:

    lib-$]              version-specific standard library path to add to @INC

    lib                 standard library path to add to @INC

    sitelib-$]          version-specific site library path to add to @INC

    sitelib             site library path to add to @INC

    vendorlib-$]        version-specific vendor library path to add to @INC

    vendorlib           vendor library path to add to @INC

    PERL*               fallback for all %ENV lookups that begin with "PERL"

Note the $] in the above is not literal. Substitute whatever version

of perl you want to honor that entry, e.g. 5.6.0. Paths must be

separated with semicolons, as usual on win32.

File Globbing

By default, perl handles file globbing using the File::Glob extension,

which provides portable globbing.

If you want perl to use globbing that emulates the quirks of DOS

filename conventions, you might want to consider using File::DosGlob

to override the internal glob() implementation. See the File::DosGlob manpage for

details.

Using perl from the command line

If you are accustomed to using perl from various command-line

shells found in UNIX environments, you will be less than pleased

with what Windows offers by way of a command shell.

The crucial thing to understand about the Windows environment is that

the command line you type in is processed twice before Perl sees it.

First, your command shell (usually CMD.EXE on Windows NT, and

COMMAND.COM on Windows 9x) preprocesses the command line, to handle

redirection, environment variable expansion, and location of the

executable to run. Then, the perl executable splits the remaining

command line into individual arguments, using the C runtime library

upon which Perl was built.

It is particularly important to note that neither the shell nor the C

runtime do any wildcard expansions of command-line arguments (so

wildcards need not be quoted). Also, the quoting behaviours of the

shell and the C runtime are rudimentary at best (and may, if you are

using a non-standard shell, be inconsistent). The only (useful) quote

character is the double quote (``). It can be used to protect spaces

and other special characters in arguments.

The Windows NT documentation has almost no description of how the

quoting rules are implemented, but here are some general observations

based on experiments: The C runtime breaks arguments at spaces and

passes them to programs in argc/argv. Double quotes can be used to

prevent arguments with spaces in them from being split up. You can

put a double quote in an argument by escaping it with a backslash and

enclosing the whole argument within double quotes. The backslash and

the pair of double quotes surrounding the argument will be stripped by

the C runtime.

The file redirection characters ``<'', ``>'', and ``|'' can be quoted by

double quotes (although there are suggestions that this may not always

be true). Single quotes are not treated as quotes by the shell or

the C runtime, they don't get stripped by the shell (just to make

this type of quoting completely useless). The caret ``^'' has also

been observed to behave as a quoting character, but this appears

to be a shell feature, and the caret is not stripped from the command

line, so Perl still sees it (and the C runtime phase does not treat

the caret as a quote character).

Here are some examples of usage of the ``cmd'' shell:

This prints two doublequotes:

    perl -e "print '\"\"' "

This does the same:

    perl -e "print \"\\\"\\\"\" "

This prints ``bar'' and writes ``foo'' to the file ``blurch'':

    perl -e "print 'foo'; print STDERR 'bar'" > blurch

This prints ``foo'' (``bar'' disappears into nowhereland):

    perl -e "print 'foo'; print STDERR 'bar'" 2> nul

This prints ``bar'' and writes ``foo'' into the file ``blurch'':

    perl -e "print 'foo'; print STDERR 'bar'" 1> blurch

This pipes ``foo'' to the ``less'' pager and prints ``bar'' on the console:

    perl -e "print 'foo'; print STDERR 'bar'" | less

This pipes ``foo\nbar\n'' to the less pager:

    perl -le "print 'foo'; print STDERR 'bar'" 2>&1 | less

This pipes ``foo'' to the pager and writes ``bar'' in the file ``blurch'':

    perl -e "print 'foo'; print STDERR 'bar'" 2> blurch | less

Discovering the usefulness of the ``command.com'' shell on Windows 9x

is left as an exercise to the reader smile

One particularly pernicious problem with the 4NT command shell for

Windows NT is that it (nearly) always treats a % character as indicating

that environment variable expansion is needed. Under this shell, it is

therefore important to always double any % characters which you want

Perl to see (for example, for hash variables), even when they are

quoted.

Building Extensions

The Comprehensive Perl Archive Network (CPAN) offers a wealth

of extensions, some of which require a C compiler to build.

Look in http://www.cpan.org/ for more information on CPAN.

Note that not all of the extensions available from CPAN may work

in the Win32 environment; you should check the information at

http://testers.cpan.org/ before investing too much effort into

porting modules that don't readily build.

Most extensions (whether they require a C compiler or not) can

be built, tested and installed with the standard mantra:

    perl Makefile.PL

    $MAKE

    $MAKE test

    $MAKE install

where $MAKE is whatever 'make' program you have configured perl to

use. Use ``perl -V:make'' to find out what this is. Some extensions

may not provide a testsuite (so ``$MAKE test'' may not do anything or

fail), but most serious ones do.

It is important that you use a supported 'make' program, and

ensure Config.pm knows about it. If you don't have nmake, you can

either get dmake from the location mentioned earlier or get an

old version of nmake reportedly available from:

 http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/nmake15.exe

Another option is to use the make written in Perl, available from

CPAN.

    http://www.cpan.org/modules/by-module/Make/

You may also use dmake. See Make above on how to get it.

Note that MakeMaker? actually emits makefiles with different syntax

depending on what 'make' it thinks you are using. Therefore, it is

important that one of the following values appears in Config.pm:

    make='nmake'        # MakeMaker emits nmake syntax

    make='dmake'        # MakeMaker emits dmake syntax

    any other value     # MakeMaker emits generic make syntax

                            (e.g GNU make, or Perl make)

If the value doesn't match the 'make' program you want to use,

edit Config.pm to fix it.

If a module implements XSUBs, you will need one of the supported

C compilers. You must make sure you have set up the environment for

the compiler for command-line compilation.

If a module does not build for some reason, look carefully for

why it failed, and report problems to the module author. If

it looks like the extension building support is at fault, report

that with full details of how the build failed using the perlbug

utility.

Command-line Wildcard Expansion

The default command shells on DOS descendant operating systems (such

as they are) usually do not expand wildcard arguments supplied to

programs. They consider it the application's job to handle that.

This is commonly achieved by linking the application (in our case,

perl) with startup code that the C runtime libraries usually provide.

However, doing that results in incompatible perl versions (since the

behavior of the argv expansion code differs depending on the

compiler, and it is even buggy on some compilers). Besides, it may

be a source of frustration if you use such a perl binary with an

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

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

entirely different kinds of wildcard expansion).

        C:\> copy con c:\perl\lib\Wild.pm

        # Wild.pm - emulate shell @ARGV expansion on shells that don't

        use File::DosGlob;

        @ARGV = map {

                      my @g = File::DosGlob::glob($_) if /[*?]/;

                      @g ? @g : $_;

                    } @ARGV;

1;

^Z

        C:\> set PERL5OPT=-MWild

        C:\> perl -le "for (@ARGV) { print }" */*/perl*.c

        p4view/perl/perl.c

        p4view/perl/perlio.c

        p4view/perl/perly.c

        perl5.005/win32/perlglob.c

        perl5.005/win32/perllib.c

        perl5.005/win32/perlglob.c

        perl5.005/win32/perllib.c

        perl5.005/win32/perlglob.c

        perl5.005/win32/perllib.c

Note there are two distinct steps there: 1) You'll have to create

Wild.pm and put it in your perl lib directory. 2) You'll need to

set the PERL5OPT? environment variable. If you want argv expansion

to be the default, just set PERL5OPT? in your default startup

environment.

If you are using the Visual C compiler, you can get the C runtime's

command line wildcard expansion built into perl binary. The resulting

binary will always expand unquoted command lines, which may not be

what you want if you use a shell that does that for you. The expansion

done is also somewhat less powerful than the approach suggested above.

Win32 Specific Extensions

A number of extensions specific to the Win32 platform are available

from CPAN. You may find that many of these extensions are meant to

be used under the Activeware port of Perl, which used to be the only

native port for the Win32 platform. Since the Activeware port does not

have adequate support for Perl's extension building tools, these

extensions typically do not support those tools either and, therefore,

cannot be built using the generic steps shown in the previous section.

To ensure smooth transitioning of existing code that uses the

ActiveState? port, there is a bundle of Win32 extensions that contains

all of the ActiveState? extensions and several other Win32 extensions from

CPAN in source form, along with many added bugfixes, and with MakeMaker?

support. This bundle is available at:

   http://www.cpan.org/modules/by-module/Win32/libwin32-0.191.zip

See the README in that distribution for building and installation

instructions. Look for later versions that may be available at the

same location.

Notes on 64-bit Windows

Windows .NET Server supports the LLP64 data model on the Intel Itanium

architecture.

The LLP64 data model is different from the LP64 data model that is the

norm on 64-bit Unix platforms. In the former, int and long are

both 32-bit data types, while pointers are 64 bits wide. In addition,

there is a separate 64-bit wide integral type, __int64. In contrast,

the LP64 data model that is pervasive on Unix platforms provides int

as the 32-bit type, while both the long type and pointers are of

64-bit precision. Note that both models provide for 64-bits of

addressability.

64-bit Windows running on Itanium is capable of running 32-bit x86

binaries transparently. This means that you could use a 32-bit build

of Perl on a 64-bit system. Given this, why would one want to build

a 64-bit build of Perl? Here are some reasons why you would bother:

Running Perl Scripts

Perl scripts on UNIX use the ``#!'' (a.k.a ``shebang'') line to indicate to the OS that it should execute the file using perl. Win32 has no comparable means to indicate arbitrary files are executables. Instead, all available methods to execute plain text files on Win32 rely on the file ``extension''. There are three methods to use this to execute perl scripts:

        pl2bat foo.pl

$0

Miscellaneous Things

A full set of HTML documentation is installed, so you should be able to use it if you have a web browser installed on your system. perldoc is also a useful tool for browsing information contained in the documentation, especially in conjunction with a pager like less (recent versions of which have Win32 support). You may have to set the PAGER environment variable to use a specific pager. ``perldoc -f foo'' will print information about the perl operator ``foo''. One common mistake when using this port with a GUI library like Tk is assuming that Perl's normal behavior of opening a command-line window will go away. This isn't the case. If you want to start a copy of perl without opening a command-line window, use the wperl executable built during the installation process. Usage is exactly the same as normal perl on Win32, except that options like -h don't work (since they need a command-line window to print to). If you find bugs in perl, you can run perlbug to create a bug report (you may have to send it manually if perlbug cannot find a mailer on your system).

voltar para o topo

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 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 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

   set PERLIO=perlio

but that may be just luck. Other AntiVirus? software may have similar issues. Some of the built-in functions do not act exactly as documented in the perlfunc manpage, and a few are not implemented at all. To avoid surprises, particularly if you have had prior exposure to Perl in other operating environments or if you intend to write code that will be portable to other environments, see the perlport manpage for a reasonably definitive list of these differences. Not all extensions available from CPAN may build or work properly in the Win32 environment. See Building Extensions. Most socket() related calls are supported, but they may not behave as on Unix platforms. See the perlport manpage for the full list. Perl requires Winsock2 to be installed on the system. If you're running Win95, you can download Winsock upgrade from here: http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp Later OS versions already include Winsock2 support. Signal handling may not behave as on Unix platforms (where it doesn't exactly ``behave'', either :). For instance, calling die() or exit() from signal handlers will cause an exception, since most implementations of signal() on Win32 are severely crippled. Thus, signals may work only for simple things like setting a flag variable in the handler. Using signals under this port should currently be considered unsupported. Please send detailed descriptions of any problems and solutions that you may find to <perlbug@perl.org>, along with the output produced by perl -V.

voltar para o topo

ACKNOWLEDGEMENTS

The use of a camel with the topic of Perl is a trademark of O'Reilly and Associates, Inc. Used with permission.

voltar para o topo

AUTHORS

Gary Ng <71564.1743@CompuServe.COM>
Gurusamy Sarathy <gsar@activestate.com>
Nick Ing-Simmons <nick@ing-simmons.net>
Jan Dubois <jand@activestate.com>
Steve Hay <steve.hay@uk.radan.com>

This document is maintained by Jan Dubois.

voltar para o topo

HISTORY

This port was originally contributed by Gary Ng around 5.003_24, and borrowed from the Hip Communications port that was available at the time. Various people have made numerous and sundry hacks since then. Borland support was added in 5.004_01 (Gurusamy Sarathy). GCC/mingw32 support was added in 5.005 (Nick Ing-Simmons). Support for PERL_OBJECT was added in 5.005 (ActiveState? Tool Corp). Support for fork() emulation was added in 5.6 (ActiveState? Tool Corp). Win9x support was added in 5.6 (Benjamin Stuhl). Support for 64-bit Windows added in 5.8 (ActiveState? Corp). Last updated: 15 February 2005

voltar para o topo

TRADUZINDO

Er Galvão Abbott <pmpoa@galvao.eti.br>

voltar para o topo

Pesquisar

Documentação

Artigos

Planeta

Eventos

Comunidade

OBSERVAÇÃO

NOME

SINOPSE

DESCRIÇÃO

Configurando Perl em Win32

Building

Testing Perl on Win32

Installation of Perl on Win32

Usage Hints for Perl on Win32

Running Perl Scripts

Miscellaneous Things

BUGS AND CAVEATS

ACKNOWLEDGEMENTS

AUTHORS

SEE ALSO

HISTORY

TRADUZINDO