[yocto] Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...

Ryan Kirkpatrick linux at rkirkpat.net
Wed Oct 9 12:52:21 PDT 2013


On Tue, 8 Oct 2013, Paul Eggleton wrote:

> Have you sent these fixes to the layer maintainer - Autif Khan 
> (autif.mlist at gmail.com) ? It would be good to get those integrated.

Yes, I did shortly after my post to the list, but I have not heard any 
response. 

Since then I have run into some issues with Mono v2.10 itself and my 
company's existing (proprietary) code base. It is an odd issue around 
events and a complex class hierarchy that I had encountered in the past 
with Mono v2.4 (but not v2.2). I traced it down to a single change in Mono 
and backed out that change for the previous product (an embedded server). 
I did report it to the Mono list at that time, but there was no simple 
test case I could share.

Anyway, I did a quick test with Mono v3.2 (from their web site on OS X) 
and the issues were no longer present. Hence, for the new product that I 
plan to use Yocto to develop, I am going to use Mono v3.2. Of course the 
current Mono layer has a lot more than we need (which is only the runtime 
and corelib, no X, xsp, etc...) but only includes support through v2.11. I 
am currently considering whether updating the existing meta-mono layer for 
v3.2 or just writing a quick recipe for just want we need from Mono.

This is complicated by a quick attempt to build the existing Mono layer 
for ARM failing. The failure was on the ARM objcopy not knowing what to do 
with mcs.exe.so as it is .NET assembly wrapped as an i386 shared object. 
This was during the generation of the debug package files, so looks like 
that process needs to be tweaked to understand this special case. 

I would welcome any advice on how to proceed with Mono v3.2 recipes and 
for building on ARM. Thanks!

---------------------------------------------------------------------------
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---------------------------------------------------------------------------



More information about the yocto mailing list