On 02/11/2013 21:49, Ryan Kirkpatrick wrote:
On Thu, 31 Oct 2013, Alex J Lennon wrote:

I see that Mono no longer seems to be building against Yocto head / 
qemux86 (for me at least) and am considering looking at a recipe to 
build the current release of Mono whilst I dig into why this is.

I wondered if you'd made any progress with this at all in the past few 
weeks?
Unfortunately I have not made any progress and probably will not for a 
while. Before I could get started on recipes, priorities on the project 
that the Mono build was for got shifted around and I have spent the past 
month on other tasks. I might be able to get back to it before the end of 
the year, but I will not mind if you beat me to it. :)

Let me know if you make any progress! Thanks! 

I have been working on this and have Mono 3.2.3 building for qemux86. I've successfully
tested it with both a simple console and Windows Forms "Hello World" application within
qemu.

I'm working on running this against an i.MX6 machine, imx6qsabresd, out
of meta-fsl-arm but it is currently failing on something related to the libgdiplus support.

I'll provide an update when I have it going.

Cheers,

Alex

---------------------------------------------------------------------------
| "For to me to live is Christ, and to die is gain." --- Phil. 1:21 (KJV) |
---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------



--

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to