two and a half steps further for WinCE cross-build

Message-ID: <022001c1f537$d2dd4f10$cb5cc3d9@vad>

p4raw-id: //depot/perl@16436

1 files changed, 30 insertions, 2 deletions

diff --git a/wince/README.compile b/wince/README.compile
index 30c3d479aa..3325402414 100644
--- a/wince/README.compile
+++ b/wince/README.compile
@@ -11,6 +11,34 @@ Socket and IO dlls compiled. Seem to work.
 
 The sequence for building a new target is:
 
-make clean      # clean up
-make all	# build for target
+make -f Makefile.ce clean	# clean up
+make -f Makefile.ce all		# build for target
 
+CROSS_NAME macro is provided to name your current cross compilation.
+It is "wince" by default, but may be any other identifier to
+differentiate and co-exist miscellaneous configurations.
+So your command often will be
+
+make -f Makefile.ce all CROSS_NAME=[my-cross-name]
+
+It is implemented an easy way to build most of module extensions.
+First, you need to do
+
+  nmake host-install CROSS_NAME=[my-cross-name]
+
+This command will install a set of files into your perl directory.
+That will allow you to do cross-compiling for your CE device.
+Those files are C libraries, h-files, Cross.pm, Config.pm. Note
+that it will use first found perl in your path. You should think about
+your PATH variable and change it at your will before copying such files.
+
+After that to do cross-compiling you need to invoke
+
+  perl -MCross Makefile.PL
+
+or
+
+  perl -MCross=[my-cross-name] Makefile.PL
+  
+to prepare Makefile, and then nmake, nmake install, as usually you do.
+'test' tartget is still not ready.