I still think we need to talk to Xamarin and point out that arm isn't a platform they can ignore going forward.
Just a quick question, will ngen still work? If the code is changed to pure native we shouldn't have any issues right?
So, I've not really worked on it for a while - I'm waiting for a compatible version of Mono (3.x) to appear in any version of Debian before doing anything about it, and with the freeze ongoing, this hasn't happened.
There are really not that many things to do, and none of them are major work:
* Remove the assumption that armhf always means armv7 (the Pi people need this, as Pi is armv6 - Debian always builds armhf for armv7 though)
* Ensure that none of the changes in the armhf branch adversely affect building/running on older soft-float ARM
Long term, it's unfortunate that these changes cannot go into upstream Mono (they're LGPL and (c) Sony, so Xamarin cannot include the changes in their non-Free MonoTouch and Mono For Android products) but I don't mind Debian being the primary source for Mono on armhf.
jkommeren wrote:(I contacted Directhex, Jo Shields, the developer of the mono-1 distro)
Thanks mr. Shields!![]()
With your permission I'd like to share the email you sent meSo, I've not really worked on it for a while - I'm waiting for a compatible version of Mono (3.x) to appear in any version of Debian before doing anything about it, and with the freeze ongoing, this hasn't happened.
There are really not that many things to do, and none of them are major work:
* Remove the assumption that armhf always means armv7 (the Pi people need this, as Pi is armv6 - Debian always builds armhf for armv7 though)
* Ensure that none of the changes in the armhf branch adversely affect building/running on older soft-float ARM
Long term, it's unfortunate that these changes cannot go into upstream Mono (they're LGPL and (c) Sony, so Xamarin cannot include the changes in their non-Free MonoTouch and Mono For Android products) but I don't mind Debian being the primary source for Mono on armhf.
I promised him a beer too for his hard workso I'm sending him a small donation via Paypal, if anyone wants to join in, his email / paypal address can be found on the github page https://github.com/directhex
Twinkletoes wrote:We have independently (with some help from Jo Shields) got Mono working a couple of weeks ago, and we're putting it through its paces here. We're about to release a set of mono binaries for Pi with installation instructions.
Twinkletoes wrote:We have independently (with some help from Jo Shields) got Mono working a couple of weeks ago, and we're putting it through its paces here. We're about to release a set of mono binaries for Pi with installation instructions.
Which bit is (c) Sony?
Bryan
Twinkletoes wrote:We have independently (with some help from Jo Shields) got Mono working a couple of weeks ago, and we're putting it through its paces here. We're about to release a set of mono binaries for Pi with installation instructions.
Which bit is (c) Sony?
Bryan
bfagioli wrote:By the way is that prior post implying that Sony owns some portion of mono? How can that be - I thought mono was open source.
plugwash wrote:bfagioli wrote:By the way is that prior post implying that Sony owns some portion of mono? How can that be - I thought mono was open source.
Just because code is opensource doesn't mean it doesn't have a copyright holder ...(some text deleted) ...Unless sony altruistically decides to do that (fat chance) the sony changes can be used by those of us who use mono under the opensource licenses but cannot go upstream.