~ubuntu-branches/ubuntu/intrepid/perl-doc-html/intrepid

<pre class="verbatim"> Microsoft Platform SDK Nov 2001 (64-bit compiler and tools)</pre>The MS Platform SDK can be downloaded from <a href="http://www.microsoft.com/">http://www.microsoft.com/</a>.

125

130

This port fully supports MakeMaker (the set of modules that

176

181

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

177

182

make for building extensions using MakeMaker.

178

183

</li>

184

<li><a name="Microsoft-Visual-C%2b%2b-2008-Express-Edition-Beta-2"></a>Microsoft Visual C++ 2008 Express Edition Beta 2

185

This free version of Visual C++ 2008 Professional contains the same compiler

186

and linker that ship with the full version, and also contains everything

187

necessary to build Perl, rather than requiring a separate download of the

188

Platform SDK like previous versions did.

189

The Beta 2 package is currently available from

190

<a href="http://msdn2.microsoft.com/en-us/express/future/default.aspx">http://msdn2.microsoft.com/en-us/express/future/default.aspx</a>

191

<a href="http://msdn2.microsoft.com/en-gb/express/future/default.aspx">http://msdn2.microsoft.com/en-gb/express/future/default.aspx</a>

192

The final release version will probably be found by searching in the Download

193

Center at <a href="http://www.microsoft.com/downloads/search.aspx?displaylang=en">http://www.microsoft.com/downloads/search.aspx?displaylang=en</a> in due

194

course.

195

Install Visual C++ 2008, then setup your environment using

196

<pre class="verbatim"> C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat</pre>

197

(assuming the default installation location was chosen).

198

Perl should now build using the win32/Makefile. You will need to edit that

199

file to set

200

<pre class="verbatim"> CCTYPE = MSVC90FREE</pre>

201

first.

202

</li>

203

<li><a name="Microsoft-Visual-C%2b%2b-2005-Express-Edition"></a>Microsoft Visual C++ 2005 Express Edition

204

This free version of Visual C++ 2005 Professional contains the same compiler

205

and linker that ship with the full version, but doesn't contain everything

206

necessary to build Perl.

207

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

208

SDK" components are required) for more header files and libraries.

209

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

210

<a href="http://www.microsoft.com/downloads/search.aspx?displaylang=en">http://www.microsoft.com/downloads/search.aspx?displaylang=en</a>. (Providing exact

211

links to these packages has proven a pointless task because the links keep on

212

changing so often.)

213

Try to obtain the latest version of the Platform SDK. Sometimes these packages

214

contain a particular Windows OS version in their name, but actually work on

215

other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK"

216

also runs on Windows XP SP2 and Windows 2000.

217

According to the download pages these packages are only supported on Windows

218

2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows

219

NT probably won't work.

220

Install Visual C++ 2005 first, then the Platform SDK. Setup your environment

221

as follows (assuming default installation locations were chosen):

222

<pre class="verbatim"> SET PlatformSDKDir=C:\Program Files\Microsoft Platform SDK</pre><pre class="verbatim"> SET PATH=%SystemRoot%\system32;%SystemRoot%;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;C:\Program Files\Microsoft Visual Studio 8\VC\BIN;C:\Program Files\Microsoft Visual Studio 8\Common7\Tools;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;%PlatformSDKDir%\Bin</pre>

223

<pre class="verbatim"> SET INCLUDE=C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE;%PlatformSDKDir%\include</pre><pre class="verbatim"> SET LIB=C:\Program Files\Microsoft Visual Studio 8\VC\LIB;C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\lib;%PlatformSDKDir%\lib</pre><pre class="verbatim"> SET LIBPATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727</pre>(The PlatformSDKDir might need to be set differently depending on which version

224

you are using. Earlier versions installed into "C:\Program Files\Microsoft SDK",

225

while the latest versions install into version-specific locations such as

226

"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2".)

227

Perl should now build using the win32/Makefile. You will need to edit that

228

file to set

229

<pre class="verbatim"> CCTYPE = MSVC80FREE</pre>

230

and to set CCHOME, CCINCDIR and CCLIBDIR as per the environment setup above.

231

</li>

179

232

<li><a name="Microsoft-Visual-C%2b%2b-Toolkit-2003"></a>Microsoft Visual C++ Toolkit 2003

180

233

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

181

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

234

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

182

235

necessary to build Perl.

183

236

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

184

237

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

192

245

changing so often.)

193

246

Try to obtain the latest version of the Platform SDK. Sometimes these packages

194

247

contain a particular Windows OS version in their name, but actually work on

195

other OS versions too. For example, the "Windows Server 2003 SP1 Platform SDK"

248

other OS versions too. For example, the "Windows Server 2003 R2 Platform SDK"

196

249

also runs on Windows XP SP2 and Windows 2000.

197

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

198

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

199

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

250

According to the download pages these packages are only supported on Windows

251

2000/XP/2003, so trying to use these tools on Windows 95/98/ME and even Windows

252

NT probably won't work.

200

253

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

201

254

Setup your environment as follows (assuming default installation locations

202

255

were chosen):

203

<pre class="verbatim"> 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

204

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

205

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</pre>Several required files will still be missing:

256

<pre class="verbatim"> SET PlatformSDKDir=C:\Program Files\Microsoft Platform SDK</pre><pre class="verbatim"> SET PATH=%SystemRoot%\system32;%SystemRoot%;C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PlatformSDKDir%\Bin;C:\Program Files\Microsoft.NET\SDK\v1.1\Bin</pre><pre class="verbatim"> SET INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit 2003\include;%PlatformSDKDir%\include;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include</pre><pre class="verbatim"> SET LIB=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;%PlatformSDKDir%\lib;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib</pre>(The PlatformSDKDir might need to be set differently depending on which version

257

you are using. Earlier versions installed into "C:\Program Files\Microsoft SDK",

258

while the latest versions install into version-specific locations such as

259

"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2".)

260

Several required files will still be missing:

206

261

<ul>

207

262

<li>

208

263

cvtres.exe is required by link.exe when using a .res file. It is actually

209

264

installed by the .NET Framework SDK, but into a location such as the

210

265

following:

211

<pre class="verbatim"> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</pre>

212

Copy it from there to C:\Program Files\Microsoft SDK\Bin

266

<pre class="verbatim"> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</pre>

267

Copy it from there to %PlatformSDKDir%\Bin

213

268

</li>

214

269

<li>

215

270

lib.exe is normally used to build libraries, but link.exe with the /lib

216

271

option also works, so change win32/config.vc to use it instead:

217

272

Change the line reading:

218

273

219

274

to:

220

275

221

276

It may also be useful to create a batch file called lib.bat in

222

277

C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin containing:

223

278

<pre class="verbatim"> @echo off

228

283

<li>

229

284

setargv.obj is required to build perlglob.exe (and perl.exe if the USE_SETARGV

230

285

option is enabled). The Platform SDK supplies this object file in source form

231

in C:\Program Files\Microsoft SDK\src\crt. Copy setargv.c, cruntime.h and

286

in %PlatformSDKDir%\src\crt. Copy setargv.c, cruntime.h and

232

287

internal.h from there to some temporary location and build setargv.obj using

233

<pre class="verbatim"> cl.exe /c /I. /D_CRTBLD setargv.c</pre>Then copy setargv.obj to C:\Program Files\Microsoft SDK\lib

288

<pre class="verbatim"> cl.exe /c /I. /D_CRTBLD setargv.c</pre>Then copy setargv.obj to %PlatformSDKDir%\lib

234

289

Alternatively, if you don't need perlglob.exe and don't need to enable the

235

290

USE_SETARGV option then you can safely just remove all mention of $(GLOBEXE)

236

291

from win32/Makefile and setargv.obj won't be required anyway.

238

293

</ul>

239

294

Perl should now build using the win32/Makefile. You will need to edit that

240

295

file to set

241

<pre class="verbatim"> CCTYPE = MSVC70FREE</pre>

296

<pre class="verbatim"> CCTYPE = MSVC70FREE</pre>

242

297

and to set CCHOME, CCINCDIR and CCLIBDIR as per the environment setup above.

243

298

</li>

244

299

<li><a name="Microsoft-Platform-SDK-64-bit-Compiler"></a>Microsoft Platform SDK 64-bit Compiler

304

359

The default value for CCHOME in the makefiles for Visual C++

305

360

may not be correct for some versions. Make sure the default exists

306

361

and is valid.

307

You may also need to comment out the <code class="inline">DELAYLOAD = ...</code>

362

You may also need to comment out the <code class="inline">DELAYLOAD = ...</code>

308

363

line in the

309

364

Makefile if you're using VC++ 6.0 without the latest service pack and

310

365

the linker reports an internal error.

366

If you are using VC++ 4.2 or earlier then you'll have to change the /EHsc

367

option in the CXX_FLAG macro to the equivalent /GX option.

311

368

If you have either the source or a library that contains des_fcrypt(),

312

369

enable the appropriate option in the makefile. A ready-to-use version

313

370

of fcrypt.c, based on the version originally written by Eric Young at

324

381

<li>

325

382

Type "dmake" (or "nmake" if you are using that make).

326

383

This should build everything. Specifically, it will create perl.exe,

327

perl58.dll at the perl toplevel, and various other extension dll's

384

perl510.dll at the perl toplevel, and various other extension dll's

328

385

under the lib\auto directory. If the build fails for any reason, make

329

386

sure you have done the previous steps correctly.

330

387

</li>

352

409

option -VI- for backward (bugward) compatibility for using the old Borland

353

410

search algorithm to locate header files.

354

411

If you run the tests on a FAT partition, you may see some failures for

355

<code class="inline"><a class="l_k" href="functions/link.html">link()</a></code> related tests:

356

<pre class="verbatim"> Failed <a class="l_w" href="Test.html">Test</a> Stat Wstat Total Fail Failed List</pre>

357

<pre class="verbatim"> ../ext/IO/lib/IO/t/io_dup.t 6 4 66.67% 2-5

358

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

359

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

360

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

361

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

362

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

363

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

364

op/write.t 47 7 14.89% 1-3 6 9-11</pre>Testing on NTFS avoids these errors.

365

Furthermore, you should make sure that during <code class="inline">make test</code>

412

<code class="inline"><a class="l_k" href="functions/link.html">link()</a></code> related tests (op/write.t, op/stat.t ...). Testing on

413

NTFS avoids these errors.

414

Furthermore, you should make sure that during <code class="inline">make test</code>

366

415

you do not

367

416

have any GNU tool packages in your path: some toolkits like Unixutils

368

include some tools (<code class="inline">type</code>

417

include some tools (<code class="inline">type</code>

369

418

for instance) which override the Windows

370

419

ones and makes tests fail. Remove them from your path while testing to

371

420

avoid these errors.

372

421

Please report any other failures as described under <a href="#BUGS-AND-CAVEATS">"BUGS AND CAVEATS"</a>.

373

422

<a name="Installation-of-Perl-on-Win32"></a><h2>Installation of Perl on Win32</h2>

374

423

Type "dmake install" (or "nmake install"). This will put the newly

375

built perl and the libraries under whatever <code class="inline">INST_TOP</code>

424

built perl and the libraries under whatever <code class="inline">INST_TOP</code>

376

425

points to in the

377

426

Makefile. It will also install the pod documentation under

378

427

379

428

and HTML versions of the same under

380

429

381

430

.

382

431

To use the Perl you just installed you will need to add a new entry to

383

your PATH environment variable: <code class="inline">$INST_TOP\bin</code>

432

your PATH environment variable: <code class="inline">$INST_TOP\bin</code>

384

433

, e.g.

385

<pre class="verbatim"> set PATH=c:\perl\bin;%PATH%</pre>If you opted to uncomment <code class="inline">INST_VER</code>

386

and <code class="inline">INST_ARCH</code>

434

<pre class="verbatim"> set PATH=c:\perl\bin;%PATH%</pre>If you opted to uncomment <code class="inline">INST_VER</code>

435

and <code class="inline">INST_ARCH</code>

387

436

in the makefile

388

437

then the installation structure is a little more complicated and you will

389

need to add two new PATH components instead: <code class="inline">$INST_TOP\$INST_VER\bin</code>

438

need to add two new PATH components instead: <code class="inline">$INST_TOP\$INST_VER\bin</code>

390

439

and

391

<code class="inline">$INST_TOP\$INST_VER\bin\$ARCHNAME</code>

440

<code class="inline">$INST_TOP\$INST_VER\bin\$ARCHNAME</code>

392

441

, e.g.

393

442

<pre class="verbatim"> set PATH=c:\perl\5.6.0\bin;c:\perl\5.6.0\bin\MSWin32-x86;%PATH%</pre><a name="Usage-Hints-for-Perl-on-Win32"></a><h2>Usage Hints for Perl on Win32</h2>

394

443

<ul>

404

453

backtick commands via PERL5SHELL. See <a href="perlrun.html">perlrun</a>.

405

454

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

406

455

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

407

<code class="inline">HKEY_CURRENT_USER\Software\Perl</code>

408

and <code class="inline">HKEY_LOCAL_MACHINE\Software\Perl</code>

456

<code class="inline">HKEY_CURRENT_USER\Software\Perl</code>

457

and <code class="inline">HKEY_LOCAL_MACHINE\Software\Perl</code>

409

458

410

459

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

411

460

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

468

517

the caret as a quote character).

469

518

Here are some examples of usage of the "cmd" shell:

470

519

This prints two doublequotes:

471

<pre class="verbatim"> perl -e "print '\"\"' "</pre>

520

<pre class="verbatim"> perl -e "print '\"\"' "</pre>

472

521

This does the same:

473

<pre class="verbatim"> perl -e "print \"\\\"\\\"\" "</pre>

522

<pre class="verbatim"> perl -e "print \"\\\"\\\"\" "</pre>

474

523

This prints "bar" and writes "foo" to the file "blurch":

475

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" > blurch</pre>

524

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" > blurch</pre>

476

525

This prints "foo" ("bar" disappears into nowhereland):

477

526

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" 2> nul</pre>This prints "bar" and writes "foo" into the file "blurch":

478

527

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" 1> blurch</pre>This pipes "foo" to the "less" pager and prints "bar" on the console:

479

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" | <a class="l_w" href="less.html">less</a></pre>

528

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" | less</pre>

480

529

This pipes "foo\nbar\n" to the less pager:

481

530

<pre class="verbatim"> perl -le "print 'foo'; print STDERR 'bar'" 2>&1 | less</pre>This pipes "foo" to the pager and writes "bar" in the file "blurch":

482

531

<pre class="verbatim"> perl -e "print 'foo'; print STDERR 'bar'" 2> blurch | less</pre>Discovering the usefulness of the "command.com" shell on Windows 9x

596

645

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

597

646

architecture.

598

647

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

599

norm on 64-bit Unix platforms. In the former, <code class="inline"><a class="l_k" href="functions/int.html">int</a></code> and <code class="inline">long</code>

648

norm on 64-bit Unix platforms. In the former, <code class="inline"><a class="l_k" href="functions/int.html">int</a></code> and <code class="inline">long</code>

600

649

are

601

650

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

602

there is a separate 64-bit wide integral type, <code class="inline">__int64</code>

651

there is a separate 64-bit wide integral type, <code class="inline">__int64</code>

603

652

. In contrast,

604

653

the LP64 data model that is pervasive on Unix platforms provides <code class="inline"><a class="l_k" href="functions/int.html">int</a></code>

605

as the 32-bit type, while both the <code class="inline">long</code>

654

as the 32-bit type, while both the <code class="inline">long</code>

606

655

type and pointers are of

607

656

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

608

657

addressability.

652

701

regular batch file to the OS, may be used. The install process

653

702

makes available the "pl2bat.bat" script which can be used to wrap

654

703

perl scripts into batch files. For example:

655

704

656

705

will create the file "FOO.BAT". Note "pl2bat" strips any

657

706

.pl suffix and adds a .bat suffix to the generated file.

658

707

If you use the 4DOS/NT or similar command shell, note that

690

739

A full set of HTML documentation is installed, so you should be

691

740

able to use it if you have a web browser installed on your

692

741

system.

693

<code class="inline">perldoc</code>

742

<code class="inline">perldoc</code>

694

743

is also a useful tool for browsing information contained

695

744

in the documentation, especially in conjunction with a pager

696

like <code class="inline"><a class="l_w" href="less.html">less</a></code> (recent versions of which have Win32 support). You may

745

like <code class="inline">less</code>

746

(recent versions of which have Win32 support). You may

697

747

have to set the PAGER environment variable to use a specific pager.

698

748

"perldoc -f foo" will print information about the perl operator

699

749

"foo".

700

One common mistake when using this port with a GUI library like <code class="inline">Tk</code>

750

One common mistake when using this port with a GUI library like <code class="inline">Tk</code>

701

751

702

752

is assuming that Perl's normal behavior of opening a command-line

703

753

window will go away. This isn't the case. If you want to start a copy

704

of <code class="inline">perl</code>

705

without opening a command-line window, use the <code class="inline">wperl</code>

754

of <code class="inline">perl</code>

755

without opening a command-line window, use the <code class="inline">wperl</code>

706

756

707

757

executable built during the installation process. Usage is exactly

708

the same as normal <code class="inline">perl</code>

709

on Win32, except that options like <code class="inline">-h</code>

758

the same as normal <code class="inline">perl</code>

759

on Win32, except that options like <code class="inline">-h</code>

710

760

711

761

don't work (since they need a command-line window to print to).

712

If you find bugs in perl, you can run <code class="inline">perlbug</code>

762

If you find bugs in perl, you can run <code class="inline">perlbug</code>

713

763

to create a

714

bug report (you may have to send it manually if <code class="inline">perlbug</code>

764

bug report (you may have to send it manually if <code class="inline">perlbug</code>

715

765

cannot

716

766

find a mailer on your system).

717

767

<a name="BUGS-AND-CAVEATS"></a><h1>BUGS AND CAVEATS</h1>

724

774

files (it seems to either catch file part written and treat it as suspicious,

725

775

or virus checker may have it "locked" in a way which inhibits miniperl

726

776

updating it). The build does complete with

727

<pre class="verbatim"> set PERLIO=perlio</pre>

777

<pre class="verbatim"> set PERLIO=perlio</pre>

728

778

but that may be just luck. Other AntiVirus software may have similar issues.

729

779

Some of the built-in functions do not act exactly as documented in

730

780

<a href="perlfunc.html">perlfunc</a>, and a few are not implemented at all. To avoid

750

800

currently be considered unsupported.

751

801

Please send detailed descriptions of any problems and solutions that

752

802

you may find to <perlbug@perl.org>, along with the output

753

produced by <code class="inline">perl -V</code>

803

produced by <code class="inline">perl -V</code>

754

804

.

755

805

<a name="ACKNOWLEDGEMENTS"></a><h1>ACKNOWLEDGEMENTS</h1>

756

806

The use of a camel with the topic of Perl is a trademark

782

832

Support for fork() emulation was added in 5.6 (ActiveState Tool Corp).

783

833

Win9x support was added in 5.6 (Benjamin Stuhl).

784

834

Support for 64-bit Windows added in 5.8 (ActiveState Corp).

785

Last updated: 30 September 2005

835

Last updated: 29 August 2007

786

836

</div>

787

837

788

838

</div>

800

850

801

851

</form>

802

852

853

803

854

<h2>Labels:</h2>

804

855

805

856

Older »