a path where perl modules are, and right C<Config.pm> in that place.
That said, C<miniperl -Ilib -MConfig -we 1> should report an error, because
-it can not find C<Config.pm>. If it does not gives an error -- wrong C<Config.pm>
+it can not find C<Config.pm>. If it does not give an error -- wrong C<Config.pm>
is substituted, and resulting binaries will be a mess.
C<miniperl -MCross -MConfig -we 1> should run okay, and it will provide right
All invokes of C<Makefile.PL> are provided with C<-MCross> so to enable cross-
compile.
-=item *
-
=back
=head2 BUILD
Normally you only need to edit C<./win32/ce-helpers/compile.bat>
to reflect your system and run it.
-File C<./wince/compile.bat> is actually a wrapper to call
+File C<./win32/ce-helpers/compile.bat> is actually a wrapper to call
C<nmake -f makefile.ce> with appropriate parameters and it accepts extra
parameters and forwards them to C<nmake> command as additional
arguments. You should pass target this way.
=item * go to C<./win32> subdirectory
-=item * edit file C<compile.bat>
+=item * edit file C<./win32/ce-helpers/compile.bat>
=item * run
compile.bat
to refer a cross-compilation that was created last time.
All questions related to building for WinCE devices could be asked in
-L<perlce-user@lists.sourceforge.net> mailing list.
+F<perlce-user@lists.sourceforge.net> mailing list.
=head1 Using Perl on WinCE
Two directories C<./win32> and C<./wince> were merged, so perlce build
process comes in C<./win32> directory.
-=over
-
+=back
=head1 AUTHORS
made further support of WinCE port.
=back
-