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, Zoltan Varga wrote: > 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 <lst...@gmail.com> wrote: > > Interesting! I haven't found any docs mentioning cross AOT, but that could > > be exactly what I'm looking for. > > > > Does this mean that if I specify armv5tel-unknown-linux-gnueabi* as a > > target to ./configure, that any time I make an AOT build it will target > > armv5tel? Would I be able to execute bytecode normally with the resultant > > mono binary on the host? I guess I'm not fully clear why I would specify > > the cross AOT target to the ./configure script for mono itself. Are there > > other implications to a normal mono binary that setting the target flag > > would have? > > > > Thanks again, > > Liam > > On Friday, May 6, 2011 at 6:59 PM, Zoltan Varga wrote: > > > Hi, > > > > > > That code is actually for cross AOT, i.e. using a runtime running on x86 > > > to generate AOT code for arm, for example. I.e. it checks host and > > > target, and not host and build. > > > > > > Zoltan > > > > > > On Sat, May 7, 2011 at 3:51 AM, Liam Staskawicz <lst...@gmail.com> wrote: > > > > 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* all > > > > seem to have entries in the ` if test "x$host" != "x$target"; ` > > > > condition. > > > > > > > > I was wondering if you could provide a bit more detail about the state > > > > of support for these targets (happily, mine is on the list). Are these > > > > not actively maintained, or not known to work, or perhaps covered by > > > > some other disclaimer? > > > > > > > > Thanks! > > > > Liam > > > > > > > > On Wednesday, May 4, 2011 at 9:00 AM, Liam Staskawicz wrote: > > > > > Ah, also - http://www.mono-project.com/Mono:ARM recommends using > > > > > scratchbox to build mono for ARM. Would be nice to clarify there as > > > > > well, if possible. > > > > > > > > > > Thanks, > > > > > Liam > > > > > On Wednesday, May 4, 2011 at 8:06 AM, Liam Staskawicz wrote: > > > > > > OK, thanks! > > > > > > > > > > > > Liam > > > > > > On Wednesday, May 4, 2011 at 2:05 AM, Zoltan Varga wrote: > > > > > > > Hi, > > > > > > > > > > > > > > We recommend compiling on the device itself if possible, using > > > > > > > distcc for example. Our configure scripts etc. are not really > > > > > > > written with cross-compilation in mind. > > > > > > > > > > > > > > Zoltan > > > > > > > > > > > > > > On Wed, May 4, 2011 at 9:04 AM, Liam Staskawicz > > > > > > > <lst...@gmail.com> wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I'm just getting set up trying to cross compile mono for an ARM > > > > > > > > target using scratchbox. The wiki page at > > > > > > > > http://www.mono-project.com/Scratchbox mentions a mono devkit, > > > > > > > > but the only address is to svn://anonsvn.mono-project.com which > > > > > > > > now redirects to github, and I can't find the subproject > > > > > > > > mentioned (garmono?) anywhere in the sources on github. > > > > > > > > > > > > > > > > Did this component not survive the transition to github? > > > > > > > > Anybody have any tips on where to find it if it still exists? > > > > > > > > > > > > > > > > Of course this is coming from the perspective of somebody > > > > > > > > searching high and low for info, but if the maintainer is still > > > > > > > > around it would be nice to update the wiki page, even to say > > > > > > > > that it's out of date :) > > > > > > > > > > > > > > > > Thanks! > > > > > > > > Liam > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Mono-devel-list mailing list > > > > > > > > Mono-devel-list@lists.ximian.com > > > > > > > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
