Cross AOT means that the resulting runtime can't run code, it will only
support the
--aot command line option, creating an AOT image which can be run on the
target platform.
I'm not sure this is what you are looking for.
Zoltan
On Sat, May 7, 2011 at 7:49 PM, Liam Staskawicz
I think I understand. So if I were interested in both running normal assemblies
on the host *and* creating AOT images for a target platform, I would simply
./configure and build 2 separate mono builds on the host?
Thanks for the quick replies btw!
Liam
On Saturday, May 7, 2011 at 10:54 AM,
On Sat, May 7, 2011 at 7:57 PM, Liam Staskawicz lst...@gmail.com wrote:
I think I understand. So if I were interested in both running normal
assemblies on the host *and* creating AOT images for a target platform, I
would simply ./configure and build 2 separate mono builds on the host?
Yes
Cheers.
On Saturday, May 7, 2011 at 11:13 AM, Zoltan Varga wrote:
On Sat, May 7, 2011 at 7:57 PM, Liam Staskawicz lst...@gmail.com wrote:
I think I understand. So if I were interested in both running normal
assemblies on the host *and* creating AOT images for a target platform, I
Actually, I just had a chance to look at the ./configure script and it looks
like there is a fair amount of support in there for cross compiling: the
targets powerpc64-ps3-linux-gnu, powerpc64-xbox360-linux-gnu, x86_64-*-nacl,
armv7l-unknown-linux-gnueabi*, and armv5tel-unknown-linux-gnueabi*