Lines Matching refs:Windows

9 perlwin32 - Perl under Windows
13 These are instructions for building Perl under Windows 7 and later.
31 will work on Windows: the README.cygwin file, which give a different
32 set of rules to build a perl for Windows.  This method will probably
38 port of Perl to the Windows platform.  This includes both 32-bit and
39 64-bit Windows operating systems.  The resulting Perl requires no
50 delivering complete gcc toolchain for MS Windows:
56 Delivers gcc toolchain building 32-bit executables (which can be used both 32 and 64 bit Windows pl…
60 Delivers gcc toolchain targeting both 64-bit Windows and 32-bit Windows
76 NOTE: If you're using a 32-bit compiler to build perl on a 64-bit Windows
84 See L</Usage Hints for Perl on Windows> below for general hints about this.
86 =head2 Setting Up Perl on Windows
100 Use the default "cmd" shell that comes with Windows.  Some versions of the
254 =head2 Testing Perl on Windows
263 Universal CRT introduced in the Windows 10 April 2018 Update, and will be fixed
279 include some tools (C<type> for instance) which override the Windows
292 =head2 Installation of Perl on Windows
312 =head2 Usage Hints for Perl on Windows
350 separated with semicolons, as usual on Windows.
366 with what Windows offers by way of a command shell.
368 The crucial thing to understand about the Windows environment is that
384 The Windows documentation describes the shell parsing rules here:
442 Discovering the usefulness of the "command.com" shell on Windows 9x
446 Windows is that it (nearly) always treats a % character as indicating
459 in the Windows environment; you should check the information at
554 =item Notes on 64-bit Windows
556 Windows .NET Server supports the LLP64 data model on the Intel Itanium
568 64-bit Windows running on Itanium is capable of running 32-bit x86
587 64-bit Windows.
601 Windows has no comparable means to indicate arbitrary files are
605 Windows rely on the file "extension".  There are three methods
614 standard with Windows.  Type "ftype /?" for a complete example of how
615 to set this up for perl scripts (Say what?  You thought Windows
652 executed.  Since you can run batch files on Windows platforms simply
674 like C<less> (recent versions of which have Windows support).  You may
684 the same as normal C<perl> on Windows, except that options like C<-h>
706 A git GUI shell extension for Windows such as TortoiseGit will cause the build
722 in the Windows environment.  See L</"Building Extensions">.
730 implementations of C<signal()> on Windows are severely crippled.
781 Support for 64-bit Windows added in 5.8 (ActiveState Corp).