#610: cross-compile configuration
-----------------------+----------------------------------------------------
 Reporter:  allison    |       Owner:  dukeleto
     Type:  roadmap    |      Status:  assigned
 Priority:  normal     |   Milestone:  2.6     
Component:  configure  |     Version:          
 Severity:  medium     |    Keywords:          
     Lang:             |       Patch:          
 Platform:  all        |  
-----------------------+----------------------------------------------------

Comment(by dukeleto):

 May I suggest that we cheat a little and use qemu attain the goal of what
 we want from cross-compiling, without actually cross-compiling.

 I stole this idea from how emacs is cross-compiled in OpenEmbedded. Here
 is the rough idea:

 1) We add some arguments to Configure.pl to specify a target architechture
 2) Our config subsystem learns how to detect if qemu is available
 3) If qemu isn't available, die if attempting to cross compile
 4) If qemu is available, start a qemu process of the wanted target
 architecture, then run the entire build process within qemu

 The output of this will be binaries for architecture X, which are actually
 compiled, through the magic unicorn farts of qemu,
 for architecture Y.

 I think that this is actually feasible in the short term, unlike
 *actually* modifying our config+build system to natively
 cross-compile, which I highly doubt will happen before the heat death of
 the universe.

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/610#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to