2005-04-11

 

Evolution to Win32 porting status

First: No, you cannot run Evolution on Windows yet. No, there isn't anything (for end-users) to "beta test" yet.

That said, there has been good progress. I have been going through Evolution's dependencies, one by one.

Here is a list of what I've been working on, listed by module name as in the GNOME CVS. I might have left out some modules by mistake. Many of the recently ported modules are certainly known to require more Win32 work, for instance to be installation location independent (like GTK+ or Pango).
Currently I am working on evolution-data-server, where the libdb subdirectory is a bit of a challenge, as it doesn't go through the normal autogen mechanism, but contains a prebuilt configure script. OTOH, there probably are prebuilt libdb's for Win32, so maybe it would be simplest to just not build it as part of e-d-s on Win32, but use an installed copy? Or does it contain some changes not in the upstream version? Also working on gal, which seems straightforward.

Comments:
Wow! Evolution aside, is this a secret evil plan to bring gnome to win32? ;)
 
About popt's upstream maintainer, I'm sure the Red Hat maintainer for the package is also the upstream. I met him in Ottawa last year, but do not remember the name right now.
 
Why do we need popt? Isn't the plan to migrate all to GOption now?
 
The plan might be to migrate to GOption, but I don't want to just wait for all the popt-using code to be converted to GOption by somebody else.

I could do it myself, but that would slow down the other work, and I want to get Evolution to at least start (even if it does nothing sensible) as quickly as possible. It's much easier to get more contributors once there is something that actually runs... After that I can go back and change popt-using code to use GOption instead.
 
Post a Comment

<< Home

This page is powered by Blogger. Isn't yours?