X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/f858446f8d2c74c0a4665f0be04b65fe90e1b08c..f6f843fb9677f20d29f6881ae85b2825c42f7b8e:/README.ce diff --git a/README.ce b/README.ce index 2ca2bf0..7481bad 100644 --- a/README.ce +++ b/README.ce @@ -20,38 +20,38 @@ software is distributed. =item * -C is built. This is a single executable (without DLL), intended +F is built. This is a single executable (without DLL), intended to run on Win32, and it will facilitate remaining build process; all binaries built after it are foreign and should not run locally. -C is built using C<./win32/Makefile>; this is part of normal +F is built using F<./win32/Makefile>; this is part of normal build process invoked as dependency from wince/Makefile.ce =item * -After C is built, C is invoked to create right C +After F is built, F is invoked to create right F in right place and its corresponding Cross.pm. -Unlike Win32 build, miniperl will not have C of host within reach; -it rather will use C from within cross-compilation directories. +Unlike Win32 build, miniperl will not have F of host within reach; +it rather will use F from within cross-compilation directories. -File C is dead simple: for given cross-architecture places in @INC -a path where perl modules are, and right C in that place. +File F is dead simple: for given cross-architecture places in @INC +a path where perl modules are, and right F in that place. That said, C should report an error, because -it can not find C. If it does not give an error -- wrong C +it can not find F. If it does not give an error -- wrong F is substituted, and resulting binaries will be a mess. C should run okay, and it will provide right -C for further compilations. +F for further compilations. =item * -During extensions build phase, a script C<./win32/buldext.pl> is invoked, -which in turn steps in C<./ext> subdirectories and performs a build of +During extensions build phase, a script F<./win32/buldext.pl> is invoked, +which in turn steps in F<./ext> subdirectories and performs a build of each extension in turn. -All invokes of C are provided with C<-MCross> so to enable cross- +All invokes of F are provided with C<-MCross> so to enable cross- compile. =back @@ -79,14 +79,14 @@ For compiling, you need following: =back Needed source files can be downloaded at -L +L =head3 Make -Normally you only need to edit C<./win32/ce-helpers/compile.bat> +Normally you only need to edit F<./win32/ce-helpers/compile.bat> to reflect your system and run it. -File C<./win32/ce-helpers/compile.bat> is actually a wrapper to call +File F<./win32/ce-helpers/compile.bat> is actually a wrapper to call C with appropriate parameters and it accepts extra parameters and forwards them to C command as additional arguments. You should pass target this way. @@ -95,9 +95,9 @@ To prepare distribution you need to do following: =over 4 -=item * go to C<./win32> subdirectory +=item * go to F<./win32> subdirectory -=item * edit file C<./win32/ce-helpers/compile.bat> +=item * edit file F<./win32/ce-helpers/compile.bat> =item * run compile.bat @@ -107,7 +107,7 @@ To prepare distribution you need to do following: =back -C has C macro, and it is used further to refer to +F has C 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 @@ -115,7 +115,7 @@ 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 C +*.bat file could fit perfectly to this purpose) and your F has proper "MACHINE" parameter set, to, say, C. compile.bat @@ -130,10 +130,10 @@ Target C prepares distribution file set. Target C performs same as C but additionally compresses distribution files into zip archive. -NOTE: during a build there could be created a number (or one) of C -for cross-compilation ("foreign" C) and those are hidden inside -C<../xlib/$(CROSS_NAME)> with other auxiliary files, but, and this is important to -note, there should be B C for host miniperl. +NOTE: during a build there could be created a number (or one) of F +for cross-compilation ("foreign" F) and those are hidden inside +F<../xlib/$(CROSS_NAME)> with other auxiliary files, but, and this is important to +note, there should be B F 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 @@ -158,16 +158,16 @@ F mailing list. PerlCE is currently linked with a simple console window, so it also works on non-hpc devices. -The simple stdio implementation creates the files C, -C and C, so you might examine them if your +The simple stdio implementation creates the files F, +F and F, so you might examine them if your console has only a limited number of cols. When exitcode is non-zero, a message box appears, otherwise the console closes, so you might have to catch an exit with status 0 in your program to see any output. -stdout/stderr now go into the files C and -C +stdout/stderr now go into the files F and +F PerlIDE is handy to deal with perlce. @@ -196,7 +196,7 @@ Semi-list for executables. =item UNIXROOTPATH -- Root for accessing some special files, i.e. C, C. +- Root for accessing some special files, i.e. F, F. =item ROWS/COLS @@ -218,7 +218,7 @@ or via the PerlIDE. =head2 REGISTRY To start perl by clicking on a perl source file, you have -to make the according entries in HKCR (see C). +to make the according entries in HKCR (see F). cereg.exe (which must be executed on a desktop pc with ActiveSync) is reported not to work on some devices. You have to create the registry entries by hand using a @@ -271,21 +271,21 @@ The port for Win32 was used as a reference. =item 5.6.0 Initial port of perl to WinCE. It was performed in separate directory -named C. This port was based on contents of C<./win32> directory. -C was not built, user must have HOST perl and properly edit -C to reflect this. +named F. This port was based on contents of F<./win32> directory. +F was not built, user must have HOST perl and properly edit +F to reflect this. =item 5.8.0 -wince port was kept in the same C<./wince> directory, and C +wince port was kept in the same F<./wince> directory, and F was used to invoke native compiler to create HOST miniperl, which then facilitates cross-compiling process. Extension building support was added. =item 5.9.4 -Two directories C<./win32> and C<./wince> were merged, so perlce build -process comes in C<./win32> directory. +Two directories F<./win32> and F<./wince> were merged, so perlce build +process comes in F<./win32> directory. =back