++ed by:

169 PAUSE users
151 non-PAUSE users.

Ricardo SIGNES 😄
and 1 contributors


README.new - Cross-compilation for linux


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.

We refer to HOST as the platform where the build is performed, and to TARGET as where final executables will run.

Basic ideas


Unlike WinCE, 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 arm cross-compilation will have extension .armo, executable files will have .arm.

After typical cross-compilation the following files will be built, among others:


(this approach may be reconsidered, however.)

build process

miniperl is built. This executable is intended to run on HOST, and it will facilitate the remaining build process; all binaries built after it are foreign (TARGET) and should not run locally (HOST).

Unlike HOST build, miniperl will not have Config.pm of HOST within reach; it rather will use the Config.pm from the cross-compilation directories. In fact, if the build process does have Config.pm within reach, this is only an indication of a mistake somewhere in the middle.

  # following command is okay:
  ./miniperl -Ilib -MCross -MConfig -e 1
  # following command should cluck, and it is bad if it does not:
  ./miniperl -Ilib -MConfig -e 1

After miniperl is built, configpm is invoked to create an appropriate Config.pm in the right place and its corresponding Cross.pm.

File Cross.pm is dead simple: for given cross-architecture places in @INC a path where perl modules are, and right Config.pm in that place.

That said, miniperl -Ilib -MConfig -we 1 should report an error, because it cannot find Config.pm. If it does not give an error, a wrong Config.pm is substituted, and resulting binaries will be a mess.

miniperl -MCross -MConfig -we 1 should run okay, and it will provide a correct Config.pm for further compilations.

During extensions build phase, the script ./ext/util/make_ext_cross is invoked.

All invocations of Makefile.PL are provided with -MCross so to enable cross-compilation.


Tools & SDK

To compile, you need the following:

  • TODO

Things to be done

  • better distinguishing of config.h/xconfig.h, dependencies

  • object files created in ./xlib/cross-name/ ?