develooper Front page | perl.perl5.porters | Postings from April 2003

RE: Cross-compiling perl 5.8.0

Thread Previous | Thread Next
Konovalov, Vadim
April 15, 2003 03:30
RE: Cross-compiling perl 5.8.0
Message ID:
> > I have all of the core modules compiled.  Initially everything
> > statically loaded, then after many more days/hours of Makefile
> > debauchery dynamically linked.
> >
> > I can now even cross-compile XS modules - Huzzah!

Perl  for WinCE also cross-compiles XS modules, but currently only those
that are part of core are built.
It creates miniperl locally and perl executable itself and modules via

When I thought about implementing generic way of cross-compiling via
Configure shell script, I found out that generation of config files is
hard-to-do. Here I finished my weak efforts and just spent some more time
doing few cleanups in WinCE cross-compilation.

As few months ago I invited everyone into discussion how to implement
cross-compilation (namely how module "" should work and when it
should be generated, and how MakeMaker will behave in cross-compilation
mode), now I also wish to agree on some kind of clear understanding of
generic cross-compiling process of perl.

> > I need advice as to what is and is not cuttable.  Peoples 
> idea of what
> > is and is not "core" is of course relative.  Those modules cut are
> Ahem.  Dare I suggest INSTALL again :-) section deceptively titled
> "Minimizing the Perl installation"

I suggest breaking compiled perl libraries into set of smaller parts, say,
unicode support, "devel", "memopize" and so on, after that user will be able
to get needed distribution by just adding needed subsets together.

Let me know if something interesting will happen in  cross-compiling.

Best wishes,

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About