Initial commit of OpenSPARC T2 architecture model.

[OpenSPARC-T2-SAM] / sam-t2 / devtools / amd64 / lib / perl5 / 5.8.8 / pod / perlce.pod

If you read this file _as_is_, just ignore the funny characters you\r
see.  It is written in the POD format (see pod/perlpod.pod) which is\r
specifically designed to be readable as is.\r
\r
=head1 NAME\r
\r
perlce - Perl for WinCE\r
\r
=head1 DESCRIPTION\r
\r
This file gives the instructions for building Perl5.8 and above for\r
WinCE.  Please read and understand the terms under which this\r
software is distributed.\r
\r
=head1 BUILD\r
\r
This section describes the steps to be performed to build PerlCE.\r
You may find additional and newer information about building perl\r
for WinCE using following URL:\r
\r
  http://perlce.sourceforge.net\r
\r
There should also be pre-built binaries there.\r
\r
Don't be confused by large size of downloaded distribution or constructed\r
binaries: entire distribution could be large for WinCE ideology, but\r
you may strip it at your wish and use only required parts.\r
\r
=head2 Tools & SDK\r
\r
For compiling, you need following:\r
\r
=over 4\r
\r
=item * Microsoft Embedded Visual Tools\r
\r
=item * Microsoft Visual C++\r
\r
=item * Rainer Keuchel's celib-sources\r
\r
=item * Rainer Keuchel's console-sources\r
\r
=back\r
\r
Needed source files can be downloaded via:\r
www.rainer-keuchel.de/wince/dirlist.html\r
\r
=head2 Make\r
\r
Please pay attention that starting from 5.8.0 miniperl *is* built\r
and it facilitates in further building process. This means that\r
in addition to compiler installation for mobile device you also need\r
to have Microsoft Visual C++ installed as well.\r
\r
On the bright side, you do not need to edit any files from ./win32\r
subdirectory. Normally you only need to edit ./wince/compile.bat\r
to reflect your system and run it.\r
\r
File ./wince/compile.bat is actually a wrapper to call\r
nmake -f makefile.ce with appropriate parameters and it accepts extra\r
parameters and forwards them to "nmake" command as additional\r
arguments. You should pass target this way.\r
\r
To prepare distribution you need to do following:\r
\r
=over 4\r
\r
=item * go to ./wince subdirectory\r
\r
=item * edit file compile.bat\r
\r
=item * run \r
  compile.bat\r
\r
=item * run \r
  compile.bat dist\r
\r
=back\r
\r
makefile.ce has CROSS_NAME macro, and it is used further to refer to\r
your cross-compilation scheme. You could assign a name to it, but this\r
is not necessary, because by default it is assigned after your machine\r
configuration name, such as "wince-sh3-hpc-wce211", and this is enough\r
to distinguish different builds at the same time. This option could be\r
handy for several different builds on same platform to perform, say,\r
threaded build. In a following example we assume that all required\r
environment variables are set properly for C cross-compiler (a special\r
*.bat file could fit perfectly to this purpose) and your compile.bat\r
has proper "MACHINE" parameter set, to, say, "wince-mips-pocket-wce300".\r
\r
  compile.bat\r
  compile.bat dist\r
  compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define"\r
  compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define" dist\r
\r
If all goes okay and no errors during a build, you'll get two independent\r
distributions: "wince-mips-pocket-wce300" and "mips-wce300-thr".\r
\r
Target 'dist' prepares distribution file set. Target 'zipdist' performs\r
same as 'dist' but additionally compresses distribution files into zip\r
archive.\r
\r
NOTE: during a build there could be created a number (or one) of Config.pm\r
for cross-compilation ("foreign" Config.pm) and those are hidden inside\r
../xlib/$(CROSS_NAME) with other auxilary files, but, and this is important to\r
note, there should be *no* Config.pm for host miniperl.\r
If you'll get an error that perl could not find Config.pm somewhere in building\r
process this means something went wrong. Most probably you forgot to\r
specify a cross-compilation when invoking miniperl.exe to Makefile.PL\r
When building an extension for cross-compilation your command line should\r
look like\r
\r
  ..\miniperl.exe -I..\lib -MCross=mips-wce300-thr Makefile.PL\r
\r
or just\r
\r
  ..\miniperl.exe -I..\lib -MCross Makefile.PL\r
\r
to refer a cross-compilation that was created last time.\r
\r
\r
If you decided to build with fcrypt.c file, please refer to README.win32\r
file, as long as all legal considerations and steps to do are exactly same \r
in this case.\r
\r
All questions related to building for WinCE devices could be asked in\r
perlce-users@lists.sourceforge.net mailing list.\r
\r
=head1 ACKNOWLEDGEMENTS\r
\r
The port for Win32 was used as a reference.\r
\r
=head1 AUTHORS\r
\r
Rainer Keuchel (keuchel@netwave.de)\r
Vadim Konovalov (vkonovalov@spb.lucent.com)\r
\r