diff options
author | Steve Hay <steve.m.hay@googlemail.com> | 2019-06-13 08:24:33 +0100 |
---|---|---|
committer | Steve Hay <steve.m.hay@googlemail.com> | 2019-06-18 13:23:46 +0100 |
commit | 79c32fc2889bdbdf21cb378e1628a84867a3ffcc (patch) | |
tree | ecbb746dd8eb95436e40e8455af214e9862ea019 /Cross/README.new | |
parent | fa068f6da2218ae85bae1e26ee7591c15276555f (diff) | |
download | perl-79c32fc2889bdbdf21cb378e1628a84867a3ffcc.tar.gz |
The Windows CE Chainsaw Massacre
Remove WinCE support as agreed in the thread starting here:
https://www.nntp.perl.org/group/perl.perl5.porters/2018/07/msg251683.html
Diffstat (limited to 'Cross/README.new')
-rw-r--r-- | Cross/README.new | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/Cross/README.new b/Cross/README.new index bcfa3b3e23..b520001303 100644 --- a/Cross/README.new +++ b/Cross/README.new @@ -9,9 +9,7 @@ README.new - Cross-compilation for linux =head1 DESCRIPTION This is second approach to linux cross-compilation, which should allow -building full perl and extensions for target platform. Cross-compilation -for linux uses similar approach and shares the same files as -cross-compilation for WinCE. +building full perl and extensions for target platform. We refer to HOST as the platform where the build is performed, and to TARGET as where final executables will run. @@ -20,7 +18,7 @@ TARGET as where final executables will run. =head3 common -Unlike WinCE, output files from GCC cross-compiler are produced in the same +Output files from GCC cross-compiler are produced in the same directory where C files are. All TARGET binaries have different extensions so to distinguish HOST and TARGET binaries. Namely, object files for C<arm> cross-compilation will have extension C<.armo>, executable files will have |