mirage, opam and cross-compiling... ?

[Christopher Greenhalgh <Chris.Greenhalgh@xxxxxxxxxxxxxxxx>]

Is there something that passes for best practice when it comes to 
cross-compiling, ocaml and opam? 

I've spent the morning looking but ocaml cross-compiling seems to be rather ad 
hoc at the moment. And the approach I've taken so far following Vouillon with 
separate target-specific opam packages doesn't seem entirely satisfactory...

it would seem "better" to be able to switch to a cross-compiler and build 
standard (or at least cross-compilation-compatible) packages auto-magically. 
And it would be super-nice if this didn't require any changes to "simple" 
packages, which in turn implies that cross-compiling tools are the default and 
the cross-compiler's ocamlbuild is wise to cross-compiling. Other build tools 
(esp. oasis) could then also be extended to turn out sensible defaults when 
cross-compiling (e.g. using BuildTools fields).

I added some notes to the end of my mirage-on-android working notes, 
https://github.com/cgreenhalgh/opensharingtoolkit/blob/master/docs/mirageonandroid.md

But I'm wondering if this is already in hand somewhere or better tackled 
otherwise?

Cheers
Chris

This message and any attachment are intended solely for the addressee and may 
contain confidential information. If you have received this message in error, 
please send it back to me, and immediately delete it.   Please do not use, copy 
or disclose the information contained in this message or in any attachment.  
Any views or opinions expressed by the author of this email do not necessarily 
reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you 
are advised to perform your own checks. Email communications with the 
University of Nottingham may be monitored as permitted by UK legislation.