perlwin32.1

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

.Sp
Install Visual \*(C+ 2008, then setup your environment using
.Sp
.Vb 1
\&        C:\eProgram Files\eMicrosoft Visual Studio 9.0\eCommon7\eTools\evsvars32.bat
.Ve
.Sp
(assuming the default installation location was chosen).
.Sp
Perl should now build using the win32/Makefile.  You will need to edit that
file to set
.Sp
.Vb 1
\&        CCTYPE = MSVC90FREE
.Ve
.Sp
first.
.IP "Microsoft Visual \*(C+ 2005 Express Edition" 4
.IX Item "Microsoft Visual  2005 Express Edition"
This free version of Visual \*(C+ 2005 Professional contains the same compiler
and linker that ship with the full version, but doesn't contain everything
necessary to build Perl.
.Sp
You will also need to download the \*(L"Platform \s-1SDK\s0\*(R" (the \*(L"Core \s-1SDK\s0\*(R" and \*(L"\s-1MDAC\s0
\&\s-1SDK\s0\*(R" components are required) for more header files and libraries.
.Sp
These packages can both be downloaded by searching in the Download Center at
http://www.microsoft.com/downloads/search.aspx?displaylang=en.  (Providing exact
links to these packages has proven a pointless task because the links keep on
changing so often.)
.Sp
Try to obtain the latest version of the Platform \s-1SDK\s0.  Sometimes these packages
contain a particular Windows \s-1OS\s0 version in their name, but actually work on
other \s-1OS\s0 versions too.  For example, the \*(L"Windows Server 2003 R2 Platform \s-1SDK\s0\*(R"
also runs on Windows \s-1XP\s0 \s-1SP2\s0 and Windows 2000.
.Sp
According to the download pages these packages are only supported on Windows
2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows
\&\s-1NT\s0 probably won't work.
.Sp
Install Visual \*(C+ 2005 first, then the Platform \s-1SDK\s0.  Setup your environment
as follows (assuming default installation locations were chosen):
.Sp
.Vb 1
\&        SET PlatformSDKDir=C:\eProgram Files\eMicrosoft Platform SDK
\&
\&        SET PATH=%SystemRoot%\esystem32;%SystemRoot%;C:\eProgram Files\eMicrosoft Visual Studio 8\eCommon7\eIDE;C:\eProgram Files\eMicrosoft Visual Studio 8\eVC\eBIN;C:\eProgram Files\eMicrosoft Visual Studio 8\eCommon7\eTools;C:\eProgram Files\eMicrosoft Visual Studio 8\eSDK\ev2.0\ebin;C:\eWINDOWS\eMicrosoft.NET\eFramework\ev2.0.50727;C:\eProgram Files\eMicrosoft Visual Studio 8\eVC\eVCPackages;%PlatformSDKDir%\eBin
\&
\&        SET INCLUDE=C:\eProgram Files\eMicrosoft Visual Studio 8\eVC\eINCLUDE;%PlatformSDKDir%\einclude
\&
\&        SET LIB=C:\eProgram Files\eMicrosoft Visual Studio 8\eVC\eLIB;C:\eProgram Files\eMicrosoft Visual Studio 8\eSDK\ev2.0\elib;%PlatformSDKDir%\elib
\&
\&        SET LIBPATH=C:\eWINDOWS\eMicrosoft.NET\eFramework\ev2.0.50727
.Ve
.Sp
(The PlatformSDKDir might need to be set differently depending on which version
you are using. Earlier versions installed into \*(L"C:\eProgram Files\eMicrosoft \s-1SDK\s0\*(R",
while the latest versions install into version-specific locations such as
\&\*(L"C:\eProgram Files\eMicrosoft Platform \s-1SDK\s0 for Windows Server 2003 R2\*(R".)
.Sp
Perl should now build using the win32/Makefile.  You will need to edit that
file to set
.Sp
.Vb 1
\&        CCTYPE = MSVC80FREE
.Ve
.Sp
and to set \s-1CCHOME\s0, \s-1CCINCDIR\s0 and \s-1CCLIBDIR\s0 as per the environment setup above.
.IP "Microsoft Visual \*(C+ Toolkit 2003" 4
.IX Item "Microsoft Visual  Toolkit 2003"
This free toolkit contains the same compiler and linker that ship with
Visual \*(C+ .NET 2003 Professional, but doesn't contain everything
necessary to build Perl.
.Sp
You will also need to download the \*(L"Platform \s-1SDK\s0\*(R" (the \*(L"Core \s-1SDK\s0\*(R" and \*(L"\s-1MDAC\s0
\&\s-1SDK\s0\*(R" components are required) for header files, libraries and rc.exe, and
\&\*(L".NET Framework \s-1SDK\s0\*(R" for more libraries and nmake.exe.  Note that the latter
(which also includes the free compiler and linker) requires the \*(L".NET
Framework Redistributable\*(R" to be installed first.  This can be downloaded and
installed separately, but is included in the \*(L"Visual \*(C+ Toolkit 2003\*(R" anyway.
.Sp
These packages can all be downloaded by searching in the Download Center at
http://www.microsoft.com/downloads/search.aspx?displaylang=en.  (Providing exact
links to these packages has proven a pointless task because the links keep on
changing so often.)
.Sp
Try to obtain the latest version of the Platform \s-1SDK\s0.  Sometimes these packages
contain a particular Windows \s-1OS\s0 version in their name, but actually work on
other \s-1OS\s0 versions too.  For example, the \*(L"Windows Server 2003 R2 Platform \s-1SDK\s0\*(R"
also runs on Windows \s-1XP\s0 \s-1SP2\s0 and Windows 2000.
.Sp
According to the download pages these packages are only supported on Windows
2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows
\&\s-1NT\s0 probably won't work.
.Sp
Install the Toolkit first, then the Platform \s-1SDK\s0, then the .NET Framework \s-1SDK\s0.
Setup your environment as follows (assuming default installation locations
were chosen):
.Sp
.Vb 1
\&        SET PlatformSDKDir=C:\eProgram Files\eMicrosoft Platform SDK
\&
\&        SET PATH=%SystemRoot%\esystem32;%SystemRoot%;C:\eProgram Files\eMicrosoft Visual C++ Toolkit 2003\ebin;%PlatformSDKDir%\eBin;C:\eProgram Files\eMicrosoft.NET\eSDK\ev1.1\eBin
\&
\&        SET INCLUDE=C:\eProgram Files\eMicrosoft Visual C++ Toolkit 2003\einclude;%PlatformSDKDir%\einclude;C:\eProgram Files\eMicrosoft Visual Studio .NET 2003\eVc7\einclude
\&
\&        SET LIB=C:\eProgram Files\eMicrosoft Visual C++ Toolkit 2003\elib;%PlatformSDKDir%\elib;C:\eProgram Files\eMicrosoft Visual Studio .NET 2003\eVc7\elib
.Ve
.Sp
(The PlatformSDKDir might need to be set differently depending on which version
you are using. Earlier versions installed into \*(L"C:\eProgram Files\eMicrosoft \s-1SDK\s0\*(R",
while the latest versions install into version-specific locations such as
\&\*(L"C:\eProgram Files\eMicrosoft Platform \s-1SDK\s0 for Windows Server 2003 R2\*(R".)
.Sp
Several required files will still be missing:
.RS 4
.IP "\(bu" 4
cvtres.exe is required by link.exe when using a .res file.  It is actually
installed by the .NET Framework \s-1SDK\s0, but into a location such as the
following:
.Sp
.Vb 1
\&        C:\eWINDOWS\eMicrosoft.NET\eFramework\ev1.1.4322
.Ve
.Sp
Copy it from there to \f(CW%PlatformSDKDir\fR%\eBin
.IP "\(bu" 4
lib.exe is normally used to build libraries, but link.exe with the /lib
option also works, so change win32/config.vc to use it instead:
.Sp
Change the line reading:
.Sp
.Vb 1
\&        ar=\*(Aqlib\*(Aq
.Ve
.Sp
to:
.Sp
.Vb 1
\&        ar=\*(Aqlink /lib\*(Aq
.Ve
.Sp
It may also be useful to create a batch file called lib.bat in
C:\eProgram Files\eMicrosoft Visual \*(C+ Toolkit 2003\ebin containing:
.Sp
.Vb 2
\&        @echo off
\&        link /lib %*
.Ve
.Sp
for the benefit of any naughty C extension modules that you might want to build
later which explicitly reference \*(L"lib\*(R" rather than taking their value from
\&\f(CW$Config\fR{ar}.
.IP "\(bu" 4
setargv.obj is required to build perlglob.exe (and perl.exe if the \s-1USE_SETARGV\s0
option is enabled).  The Platform \s-1SDK\s0 supplies this object file in source form
in \f(CW%PlatformSDKDir\fR%\esrc\ecrt.  Copy setargv.c, cruntime.h and
internal.h from there to some temporary location and build setargv.obj using
.Sp
.Vb 1
\&        cl.exe /c /I. /D_CRTBLD setargv.c
.Ve
.Sp
Then copy setargv.obj to \f(CW%PlatformSDKDir\fR%\elib
.Sp
Alternatively, if you don't need perlglob.exe and don't need to enable the
\&\s-1USE_SETARGV\s0 option then you can safely just remove all mention of $(\s-1GLOBEXE\s0)
from win32/Makefile and setargv.obj won't be required anyway.
.RE
.RS 4
.Sp
Perl should now build using the win32/Makefile.  You will need to edit that
file to set
.Sp
.Vb 1
\&        CCTYPE = MSVC70FREE
.Ve
.Sp
and to set \s-1CCHOME\s0, \s-1CCINCDIR\s0 and \s-1CCLIBDIR\s0 as per the environment setup above.
.RE
.IP "Microsoft Platform \s-1SDK\s0 64\-bit Compiler" 4
.IX Item "Microsoft Platform SDK 64-bit Compiler"
The nmake that comes with the Platform \s-1SDK\s0 will suffice for building
Perl.  Make sure you are building within one of the \*(L"Build Environment\*(R"
shells available after you install the Platform \s-1SDK\s0 from the Start Menu.
.IP "MinGW release 3 with gcc" 4
.IX Item "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:
.Sp
.Vb 1
\&    http://www.mingw.org/
.Ve
.Sp
Perl also compiles with earlier releases of gcc (2.95.2 and up).  See below
for notes about using earlier versions of MinGW/gcc.
.Sp
You also need dmake.  See \*(L"Make\*(R" above on how to get it.
.IP "MinGW release 1 with gcc" 4
.IX Item "MinGW release 1 with gcc"
The MinGW\-1.1 bundle contains gcc\-2.95.3.
.Sp
Make sure you install the binaries that work with \s-1MSVCRT\s0.DLL as indicated
in the \s-1README\s0 for the \s-1GCC\s0 bundle.  You may need to set up a few environment
variables (usually ran from a batch file).
.Sp
There are a couple of problems with the version of gcc\-2.95.2\-msvcrt.exe
released 7 November 1999:
.RS 4
.IP "\(bu" 4
It left out a fix for certain command line quotes.  To fix this, be sure
to download and install the file fixes/quote\-fix\-msvcrt.exe from the above
ftp location.
.IP "\(bu" 4
The definition of the fpos_t type in stdio.h may be wrong.  If your
stdio.h has this problem, you will see an exception when running the
test t/lib/io_xs.t.  To fix this, change the typedef for fpos_t from
\&\*(L"long\*(R" to \*(L"long long\*(R" in the file i386\-mingw32msvc/include/stdio.h,
and rebuild.
.RE
.RS 4
.Sp
A potentially simpler to install (but probably soon-to-be-outdated) bundle
of the above package with the mentioned fixes already applied is available
here:
.Sp
.Vb 2
\&    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
.Ve
.RE
.Sh "Building"
.IX Subsection "Building"
.IP "\(bu" 4
Make sure you are in the \*(L"win32\*(R" subdirectory under the perl toplevel.
This directory contains a \*(L"Makefile\*(R" that will work with
versions of nmake that come with Visual \*(C+ or the Platform \s-1SDK\s0, and
a dmake \*(L"makefile.mk\*(R" that will work for all supported compilers.  The
defaults in the dmake makefile are setup to build using MinGW/gcc.
.IP "\(bu" 4
Edit the makefile.mk (or Makefile, if you're using nmake) and change
the values of \s-1INST_DRV\s0 and \s-1INST_TOP\s0.   You can also enable various
build flags.  These are explained in the makefiles.
.Sp
Note that it is generally not a good idea to try to build a perl with
\&\s-1INST_DRV\s0 and \s-1INST_TOP\s0 set to a path that already exists from a previous
build.  In particular, this may cause problems with the
lib/ExtUtils/t/Embed.t test, which attempts to build a test program and
may end up building against the installed perl's lib/CORE directory rather
than the one being tested.
.Sp
You will have to make sure that \s-1CCTYPE\s0 is set correctly and that
\&\s-1CCHOME\s0 points to wherever you installed your compiler.
.Sp
The default value for \s-1CCHOME\s0 in the makefiles for Visual \*(C+
may not be correct for some versions.  Make sure the default exists
and is valid.
.Sp
You may also need to comment out the \f(CW\*(C`DELAYLOAD = ...\*(C'\fR line in the
Makefile if you're using \s-1VC++\s0 6.0 without the latest service pack and
the linker reports an internal error.
.Sp
If you are using \s-1VC++\s0 4.2 or earlier then you'll have to change the /EHsc
option in the \s-1CXX_FLAG\s0 macro to the equivalent /GX option.
.Sp
If you have either the source or a library that contains \fIdes_fcrypt()\fR,
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
ftp://ftp.funet.fi/pub/crypt/mirrors/dsi/libdes/, is bundled with the
distribution and \s-1CRYPT_SRC\s0 is set to use it.
Alternatively, if you have built a library that contains \fIdes_fcrypt()\fR,
you can set \s-1CRYPT_LIB\s0 to point to the library name.
Perl will also build without \fIdes_fcrypt()\fR, but the \fIcrypt()\fR builtin will
fail at run time.
.Sp
If you want build some core extensions statically into perl's dll, specify
them in the \s-1STATIC_EXT\s0 macro.
.Sp
Be sure to read the instructions near the top of the makefiles carefully.
.IP "\(bu" 4
Type \*(L"dmake\*(R" (or \*(L"nmake\*(R" if you are using that make).
.Sp
This should build everything.  Specifically, it will create perl.exe,