WinCE port addition

From: "Konovalov, Vadim" <vkonovalov@spb.lucent.com>
Message-ID: <845FCFF2D4C0FC468B485E8777C7A00C200D42@cio-test001.spb.lucent.com>

p4raw-id: //depot/perl@20219

1 files changed, 54 insertions, 8 deletions

diff --git a/README.ce b/README.ce
index 23378a98dd..e8d4c49292 100644
--- a/README.ce
+++ b/README.ce
@@ -16,12 +16,16 @@ software is distributed.
 
 This section describes the steps to be performed to build PerlCE.
 You may find additional and newer information about building perl
-for WincE using following URL:
+for WinCE using following URL:
 
   http://perlce.sourceforge.net
 
 There should also be pre-built binaries there.
 
+Don't be confused by large size of downloaded distribution or constructed
+binaries: entire distribution could be large for WinCE ideology, but
+you may strip it at your wish and use only required parts.
+
 =head2 Tools & SDK
 
 For compiling, you need following:
@@ -57,11 +61,7 @@ nmake -f makefile.ce with appropriate parameters and it accepts extra
 parameters and forwards them to "nmake" command as additional
 arguments. You should pass target this way.
 
-Currently default target build all required perls, also there exists
-target 'dist' that prepares distribution file set. Other targets
-are currently in development stage.
-
-So, to prepare distribution you need to do following:
+To prepare distribution you need to do following:
 
 =over 4
 
@@ -77,8 +77,54 @@ So, to prepare distribution you need to do following:
 
 =back
 
-Before you start, you need to build celib.dll and w32console.
-See instructions in these packages for building.
+makefile.ce has CROSS_NAME macro, and it is used further to refer to
+your cross-compilation scheme. You could assign a name to it, but this
+is not necessary, because by default it is assigned after your machine
+configuration name, such as "wince-sh3-hpc-wce211", and this is enough
+to distinguish different builds at the same time. This option could be
+handy for several different builds on same platform to perform, say,
+threaded build. In a following example we assume that all required
+environment variables are set properly for C cross-compiler (a special
+*.bat file could fit perfectly to this purpose) and your compile.bat
+has proper "MACHINE" parameter set, to, say, "wince-mips-pocket-wce300".
+
+  compile.bat
+  compile.bat dist
+  compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define"
+  compile.bat CROSS_NAME=mips-wce300-thr "USE_ITHREADS=define" "USE_IMP_SYS=define" "USE_MULTI=define" dist
+
+If all goes okay and no errors during a build, you'll get two independent
+distributions: "wince-mips-pocket-wce300" and "mips-wce300-thr".
+
+Target 'dist' prepares distribution file set. Target 'zipdist' performs
+same as 'dist' but additionally compresses distribution files into zip
+archive.
+
+NOTE: during a build there could be created a number (or one) of Config.pm
+for cross-compilation ("foreign" Config.pm) and those are hidden inside
+../xlib/$(CROSS_NAME) with other auxilary files, but, and this is important to
+note, there should be *no* Config.pm for host miniperl.
+If you'll get an error that perl could not find Config.pm somewhere in building
+process this means something went wrong. Most probably you forgot to
+specify a cross-compilation when invoking miniperl.exe to Makefile.PL
+When building an extension for cross-compilation your command line should
+look like
+
+  ..\miniperl.exe -I..\lib -MCross=mips-wce300-thr Makefile.PL
+
+or just
+
+  ..\miniperl.exe -I..\lib -MCross Makefile.PL
+
+to refer a cross-compilation that was created last time.
+
+
+If you decided to build with fcrypt.c file, please refer to README.win32
+file, as long as all legal considerations and steps to do are exactly same 
+in this case.
+
+All questions related to building for WinCE devices could be asked in
+perlce-users@lists.sourceforge.net mailing list.
 
 =head1 Acknowledgements