Mono for the X1000

.....

@nicholastaylor

Well you should start by having an understanding of programming on the Amiga. It would not hurt to start with the Rom kernel reference manuals, or "RKM's" (which you can find online if you are saavy enough, then start looking at some example code, trying to compile small things.

Next up would be to look at the OS 4.1 SDK, 53.20, which was just recently released on Hyperion's website.

@nicholastaylor

Maybe you can check on amigabounty? Maybe there can be a bounty for this? Split it up in parts or something?

@nicholastaylor

There's a good guide to porting Mono on the Mono homepage, it already supports PowerPC which is probably the biggest task, but still looks rather involved.

I'd be more interested in Moonlight (which probably needs Mono ported first anyway), however since ITVPlayer ditched Silverlight I don't know of anything useful which uses it!

@nicholastaylor

The first challenge is going to be the POSIX/pthreads bits in the JIT itself. ixemul + the AOS4 pthreads implementation might get you reasonably far.

The biggest challenge, however, would be porting the various native parts of the runtime libraries. GUI toolkits etc.

It depends a lot what your goals are. If you "just" want Mono on X1000, that's a *lot* easier than getting something complete enough to run most C# apps. The former could be done with thin mappings to AmigaOS, while the latter requires supporting a lot of other libraries as well.

@vidarh
Quote:

ixemul is not supported in the Amiga OS4 SDK, and if it was mixing it with native pthreads would probably be a bad idea!

.....

@nicholastaylor

I wish you good luck and lots of perseverance. This is going to be hard...

@nicholastaylor

vidarh wrote:
Quote:
and you responded a.o.:
Quote:
The actual language is in fact not that big a part of the implementation of a typical .NET project. Most of the functionality you need will be something you call in the .NET framework, which consists of a huge amount of runtime libraries, DLLs (on Windows). These are the same whichever language (of the .NET compatible ones) you code in. This is not only GUI toolkits, but also a lot of the data structures, storage, file handling and communication basics needed in most applications.

I guess that would be what vidarh is referring to. "Most C# apps" is a high goal, not because the C# part is big, but because most C# apps will also be typical .NET apps which draw heavily on the .NET framework. (Substitute "Mono" for ".NET" in the above wherever it makes sense; I haven't had any experience with Mono myself yet.)

Best regards,

Niels