Re: [anjuta-devel] 3.10 cycle plans

[Johannes Schmid <jhs jsschmid de>]

Hey Arnel!

> What about porting Anjuta itself to Windows? I tried cross-compiling it 
> today, disabling some POSIX-specific code. It can only edit files 
> (without symbol-viewer, completion, etc.) currently. Autotools also 
> works, but compiling and running doesn't work yet. Symbol Viewer needs 
> some changes for shared memory. Glade seems to work. Terminal will never 
> work since it needs VTE. Other plugins that don't work usually needs 
> fork, waitpid and execlp porting, and some fixing for MIME (which is not 
> fully supported by Windows, most files have application/x-ext-* MIME 
> type). It also has to be fixed so that paths will be created on runtime.

There was even a README entry about porting to Windows :)

But it seems interesting to me over all despite that I don't own any
windows license privately anymore. In the past we more or less tried to
use GLib methods whereever possible and those are usually implemented
for POSIX, Windows and Mac, especially things like IO-Channels. There is
probably not much work needed to make things working in a win32 fashion
using #ifdef.

What is more interesting is the implementation of fork() if not using
cygwin, which might require a new code path but there are probably
various examples to do that.

Then the symbol-database could actually be more difficult but I don't
know much about shared memory.

Most important would be to create an installer of course because
otherwise there won't be many people that would actually be able to
build things correctly.

So, patches accepted :)

Regards,
Johannes