1PERLCE(1) Perl Programmers Reference Guide PERLCE(1)
2
6 perlce - Perl for WinCE
7
9 DESCRIPTION
10 This file gives the instructions for building Perl5.8 and above for
11 WinCE. Please read and understand the terms under which this software
12 is distributed.
13 General explanations on cross-compiling WinCE
15 · "miniperl" is built. This is a single executable (without DLL),
16 intended to run on Win32, and it will facilitate remaining build
17 process; all binaries built after it are foreign and should not run
18 locally.
19 "miniperl" is built using "./win32/Makefile"; this is part of
21 normal build process invoked as dependency from wince/Makefile.ce
22 · After "miniperl" is built, "configpm" is invoked to create right
24 "Config.pm" in right place and its corresponding Cross.pm.
25 Unlike Win32 build, miniperl will not have "Config.pm" of host
27 within reach; it rather will use "Config.pm" from within cross-
28 compilation directories.
29 File "Cross.pm" is dead simple: for given cross-architecture places
31 in @INC a path where perl modules are, and right "Config.pm" in
32 that place.
33 That said, "miniperl -Ilib -MConfig -we 1" should report an error,
35 because it can not find "Config.pm". If it does not give an error
36 -- wrong "Config.pm" is substituted, and resulting binaries will be
37 a mess.
38 "miniperl -MCross -MConfig -we 1" should run okay, and it will
40 provide right "Config.pm" for further compilations.
41 · During extensions build phase, a script "./win32/buldext.pl" is
43 invoked, which in turn steps in "./ext" subdirectories and performs
44 a build of each extension in turn.
45 All invokes of "Makefile.PL" are provided with "-MCross" so to
47 enable cross- compile.
48 BUILD
50 This section describes the steps to be performed to build PerlCE. You
51 may find additional information about building perl for WinCE at
52 <http://perlce.sourceforge.net> and some pre-built binaries.
53 Tools & SDK
55 For compiling, you need following:
57 · Microsoft Embedded Visual Tools
59 · Microsoft Visual C++
61 · Rainer Keuchel's celib-sources
63 · Rainer Keuchel's console-sources
65 Needed source files can be downloaded at
67 <http://www.rainer-keuchel.de/wince/dirlist.html>
68 Make
70 Normally you only need to edit "./win32/ce-helpers/compile.bat" to
72 reflect your system and run it.
73 File "./win32/ce-helpers/compile.bat" is actually a wrapper to call
75 "nmake -f makefile.ce" with appropriate parameters and it accepts extra
76 parameters and forwards them to "nmake" command as additional
77 arguments. You should pass target this way.
78 To prepare distribution you need to do following:
80 · go to "./win32" subdirectory
82 · edit file "./win32/ce-helpers/compile.bat"
84 · run
86 compile.bat
87 · run
89 compile.bat dist
90 "Makefile.ce" has "CROSS_NAME" macro, and it is used further to refer
92 to your cross-compilation scheme. You could assign a name to it, but
93 this is not necessary, because by default it is assigned after your
94 machine configuration name, such as "wince-sh3-hpc-wce211", and this is
95 enough to distinguish different builds at the same time. This option
96 could be handy for several different builds on same platform to
97 perform, say, threaded build. In a following example we assume that all
98 required environment variables are set properly for C cross-compiler (a
99 special *.bat file could fit perfectly to this purpose) and your
100 "compile.bat" has proper "MACHINE" parameter set, to, say,
101 "wince-mips-pocket-wce300".
102 compile.bat
104 compile.bat dist
105 compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define"
106 compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define" dist
107 If all goes okay and no errors during a build, you'll get two
109 independent distributions: "wince-mips-pocket-wce300" and
110 "mips-wce300-thr".
111 Target "dist" prepares distribution file set. Target "zipdist" performs
113 same as "dist" but additionally compresses distribution files into zip
114 archive.
115 NOTE: during a build there could be created a number (or one) of
117 "Config.pm" for cross-compilation ("foreign" "Config.pm") and those are
118 hidden inside "../xlib/$(CROSS_NAME)" with other auxilary files, but,
119 and this is important to note, there should be no "Config.pm" for host
120 miniperl. If you'll get an error that perl could not find Config.pm
121 somewhere in building process this means something went wrong. Most
122 probably you forgot to specify a cross-compilation when invoking
123 miniperl.exe to Makefile.PL When building an extension for cross-
124 compilation your command line should look like
125 ..\miniperl.exe -I..\lib -MCross=mips-wce300-thr Makefile.PL
127 or just
129 ..\miniperl.exe -I..\lib -MCross Makefile.PL
131 to refer a cross-compilation that was created last time.
133 All questions related to building for WinCE devices could be asked in
135 perlce-user@lists.sourceforge.net mailing list.
136
138 DESCRIPTION
139 PerlCE is currently linked with a simple console window, so it also
140 works on non-hpc devices.
141 The simple stdio implementation creates the files "stdin.txt",
143 "stdout.txt" and "stderr.txt", so you might examine them if your
144 console has only a liminted number of cols.
145 When exitcode is non-zero, a message box appears, otherwise the console
147 closes, so you might have to catch an exit with status 0 in your
148 program to see any output.
149 stdout/stderr now go into the files "/perl-stdout.txt" and
151 "/perl-stderr.txt."
152 PerlIDE is handy to deal with perlce.
154 LIMITATIONS
156 No fork(), pipe(), popen() etc.
157 ENVIRONMENT
159 All environment vars must be stored in HKLM\Environment as strings.
160 They are read at process startup.
161 PERL5LIB
163 Usual perl lib path (semi-list).
164 PATH
166 Semi-list for executables.
167 TMP - Tempdir.
169 UNIXROOTPATH
171 - Root for accessing some special files, i.e. "/dev/null",
172 "/etc/services".
173 ROWS/COLS
175 - Rows/cols for console.
176 HOME
178 - Home directory.
179 CONSOLEFONTSIZE
181 - Size for console font.
182 You can set these with cereg.exe, a (remote) registry editor or via the
184 PerlIDE.
185 REGISTRY
187 To start perl by clicking on a perl source file, you have to make the
188 according entries in HKCR (see "ce-helpers/wince-reg.bat"). cereg.exe
189 (which must be executed on a desktop pc with ActiveSync) is reported
190 not to work on some devices. You have to create the registry entries
191 by hand using a registry editor.
192 XS
194 The following Win32-Methods are built-in:
195 newXS("Win32::GetCwd", w32_GetCwd, file);
197 newXS("Win32::SetCwd", w32_SetCwd, file);
198 newXS("Win32::GetTickCount", w32_GetTickCount, file);
199 newXS("Win32::GetOSVersion", w32_GetOSVersion, file);
200 newXS("Win32::IsWinNT", w32_IsWinNT, file);
201 newXS("Win32::IsWin95", w32_IsWin95, file);
202 newXS("Win32::IsWinCE", w32_IsWinCE, file);
203 newXS("Win32::CopyFile", w32_CopyFile, file);
204 newXS("Win32::Sleep", w32_Sleep, file);
205 newXS("Win32::MessageBox", w32_MessageBox, file);
206 newXS("Win32::GetPowerStatus", w32_GetPowerStatus, file);
207 newXS("Win32::GetOemInfo", w32_GetOemInfo, file);
208 newXS("Win32::ShellEx", w32_ShellEx, file);
209 BUGS
211 Opening files for read-write is currently not supported if they use
212 stdio (normal perl file handles).
213 If you find bugs or if it does not work at all on your device, send
215 mail to the address below. Please report the details of your device
216 (processor, ceversion, devicetype (hpc/palm/pocket)) and the date of
217 the downloaded files.
218 INSTALLATION
220 Currently installation instructions are at
221 <http://perlce.sourceforge.net/>.
222 After installation & testing processes will stabilize, information will
224 be more precise.
225
227 The port for Win32 was used as a reference.
228
230 5.6.0
231 Initial port of perl to WinCE. It was performed in separate
232 directory named "wince". This port was based on contents of
233 "./win32" directory. "miniperl" was not built, user must have HOST
234 perl and properly edit "makefile.ce" to reflect this.
235 5.8.0
237 wince port was kept in the same "./wince" directory, and
238 "wince/Makefile.ce" was used to invoke native compiler to create
239 HOST miniperl, which then facilitates cross-compiling process.
240 Extension building support was added.
241 5.9.4
243 Two directories "./win32" and "./wince" were merged, so perlce
244 build process comes in "./win32" directory.
245
247 Rainer Keuchel <coyxc@rainer-keuchel.de>
248 provided initial port of Perl, which appears to be most essential
249 work, as it was a breakthrough on having Perl ported at all. Many
250 thanks and obligations to Rainer!
251 Vadim Konovalov
253 made further support of WinCE port.
254perl v5.10.1 2009-08-22 PERLCE(1)