During the last Novell HackWeek, me, Torello Querci and Jae Stutzman work a little on Mono packages for Maemo, we also worked a little on Tomboy port to Maemo. Last weekend I just released latest Mono for Maemo packages, the news include WinForms, ADO.NET, and Maemo-Sharp for Maemo 4 (OS2008).

If you want to play a little with the packages just add this repository to your N810:

deb http://go-mono.com/maemo chinook test

Sometimes pictures say more than a thousand words:


MonoCalendar (WinForms) running on N810



CSharpTetris (also WinForms) game running on my N810

And whoever wants to run Tomboy on N8xx devices, this is the one click install.




Packages are in test repositories for now because I am not sure about the way how we make packages available, looks a little hard to manage lots of small packages, we have now about 30 mono packages, we use the same package conventions of Mono for Debian/Ubuntu but maybe that is not the best way, as example, Python is distributed for Maemo in only one big package.

One big package looks bad for me so, my idea is to have only few packages and only Mono 2.0 (gmcs) stuff available:

• mono-runtime
• mono-system (including libralies, maemo-sharp and gtk-sharp)
• mono-winforms
• mono-data

If you have any idea about a better division of packages or some ideas, please send us a comment and we will check it for next version.

In my last article I blogged about how to create Mono bindings using GAPI, I used it to create WebKit-Sharp.

After a quick search in Google I found another implementation of WebKit bindings for Mono, you can find them there (http://cmartin.tk/webkitgtk-sharp.html), the problem is that those bindings were done by hand without using GAPI, probably because the author didn't use "gapi2-fixup" to customize and fix some information about webkit (You can find more information about it here).

Well, today I have just committed some of my local changes to webkit-sharp and the amazing "FunnyBrowser" sample, I have been using "FunnyBrowser" as my default browser now for one week and for basic navigation it works faster and uses less resources than Firefox.

Next weekend I am also planning to make packages available for Maemo if webkit works on it, I will keep you guys posted.



We haven't released webkit-sharp yet but you can found sources here:

http://anonsvn.mono-project.com/viewcvs/trunk/webkit-sharp.tar.gz

OpenSUSE 10.3 packages are also available (including libwebkit) on my repository in the OpenSUSE Build Service:

http://download.opensuse.org/repositories/home:/ecanuto:/webkit/openSUSE_10.3/

I have plans to release FunnyBrowser as package when it works with GMail without problems.

Ok, I promised several blog entries about GARMONO. However, for the last couple of weeks I've been busy fixing some issues with the WinForms DataGrid, which I will talk about in another entry. Today, let us talk about GARMONO and how it can help us automatically create Mono packages for Maemo.

One of the problems I ran into when I created the first set of Mono packages for Maemo was that it was a hard task with lots of procedures. A few weeks ago, during hack week, we decide to automate the process using GARMONO (when I say "we" I mean, Torello Querci, Jae Stutzman, and myself) and it has proven to be a very good idea. For those of you that may not understand what GARMONO is, think of it as a build-script that works within scratchbox to automate some of the more tedious tasks that would have to be done by hand or with other scripts. GARMONO provides a single "make" command that takes care of downloading mono src and creating deb files, etc. However GARMONO alone will not produce maemo packages, this is where Scratchbox comes in.

Maemo uses Scratchbox for cross-compilation. Scratchbox provides a build environment with all of the maemo provided dependencies so that developers can produce Maemo binaries. We need to use Scratchbox to create the platform (ARM) specific things that the mono runtime requires. Scratchbox uses QEMU for ARM emulation, the problem is that some ARM syscalls (242, 264, 299) are not yet implemented in QEMU. These missing syscalls can cause problems in MCS, making it impossible to compile assemblies for ARM. The solution is to create a Scratchbox devkit. It provides a set of tools that can be executed on the host instead of target device and thus reduces the time needed to build packages.

Instead of providing the instructions on how to build the devkit in this blog, I will just point you to the wiki entry that we created on the Mono Wiki:
http://www.mono-project.com/Scratchbox

Please know that in order for you to execute these instructions you must first to have Scratchbox and Maemo SDK installed, instructions can be found here.

Again, I would like to credit Jae Stutzman and Torello Querci for their support of the work in GARMONO and Maemo.

One of hard things of cross-platform development with WinForms is that you always need to test in both Linux and Windows. My second development environment is Cygwin running on Windows but when I need to travel somewhere, I also need to have this Cygwin environment available on my Windows Virtual Machine.

Andreia made a very good tutorial about how to create a Mono+Cygwin Installation and Compilation, and I've used it for years. However, sometimes I lose my environment or have problems when trying to compile a new Mono version and I need to install it over and over.

When I noticed that Gnome had GARNOME (a build tool that allows users to build the GNOME Desktop), I thought that it would be nice if we had one tool like this not only to build Mono but also to install some dependencies on environments like Cygwin. That is how GARMONO was born. GARMONO is based on GAR software and if you need moreinformation about it a good place is to check is this article in Linux Journal.

We can use GARMONO to build Mono on Cygwin, Linux, Maemo and also use it to generate packages (.deb for Nokia N810). So, I will start a series of blog entries about this, but today let us talk about Cygwin.

Compiling and installing Mono on Cygwin can be a hard task but I believe it is much easier using GARMONO. First, you must get your Cygwin environment installed and working. Also, make sure that you have installed automake, bison, gcc, gdb and libtool. These packages are necessary if you want to build anything.

So, now let us download and unpack GARMONO. For this, log into your Cygwin environment and type:

# wget http://anonsvn.mono-project.com/viewcvs/trunk/release/garmono.tar.gz
# tar -xzvf garmono.tar.gz
# cd garmono

Now we just need to build Mono:

# make cygwin/build

And that is all! GARMONO will download and install all dependencies and later will download and install Mono in your ~/mono. It will also create a bash script with all environment vars needed to use Mono. To call this script just type:

# source ~/mono/bin/monoenv

You could also put this line in your .profile or .bash_profile script.

Over the next several blog entries, I will give more tips about GARMONO and how use it in Maemo and Linux environments.

Last weekend finally I was finished the Mono packages for Nokia 770/800 devices, Wade helped me to get apt repository available. To make things more easy we made available an "Single Install Click" for Mono runtime and for Paco's PEditGtkSharp an small gtk-sharp text editior. Dependency check really make life easy, as example when you install PEditGtkSharp all need stuff (mono-runtime, gtk-sharp and maemo-sharp) is also installed.



For who wants install packages by hand, the N770 repository is:

  deb http://go-mono.com/maemo mistral user

and N800:

  deb http://go-mono.com/maemo bora user

Scratchbox developer kit is also available as binary. An wiki entry is also set up to give more information about Mono on Maemo.

The screenshot comes from Torello Querci. Unfortunately I cant buy Nokia N800 from Brazil, today I receive a mail from Nokia and they saw that to buy a device I must have a credit card emitted in USA. Maybe they can also restrict the Maemo download for non USA/Europe people ;-)