Windows Port

[nmn]

Sorry, It is not done yet. This is discussion of it.

1. I will be submitting code soon today. I made a crude port but then realized I wanted to improve the code organization more.
2. The windows port will probably lack a GUI initially.



So far, I had gotten it to build but not run. However, I want to quickly rewrite the port now that I know what must be done.

Anyways, Suggestions on things I should be aiming at? Should we just throw up the GTK GUI initially?

[X-Fi6]

Yeah initially you should use GTK for the Windows port as to avoid confusions between the Windows port's GUI and all other OS's GUI.

Apart from that I don't really know what you should be aiming at. I want the Windows port to stay alive because after all Mupen64 stands for Multi Platform Emulator for n64 and without the Windows port it doesn't feel like it's complete.

It's also a great base for curious people to code in their own stuff that they would personally want. Without a Windows port they can't do that.

[_Zack_]

Sorry, It is not done yet. This is discussion of it.

1. I will be submitting code soon today. I made a crude port but then realized I wanted to improve the code organization more.
2. The windows port will probably lack a GUI initially.

So far, I had gotten it to build but not run. However, I want to quickly rewrite the port now that I know what must be done.

Anyways, Suggestions on things I should be aiming at? Should we just throw up the GTK GUI initially?

I think the aim should be on keeping the Linux fixes current with the Windows build. All those core & plugin updates and new features should defiantly be in the Windows build too.

Why not just use the Gui from V0.5 nmm?

[nmn]

The old GUI would work but it would require too much change.

BTW, the port should allow us to merge into the latest version so that we will always be current with updates.

[Richard42]

So far, I had gotten it to build but not run. However, I want to quickly rewrite the port now that I know what must be done.

Anyways, Suggestions on things I should be aiming at? Should we just throw up the GTK GUI initially?

For the sake of simplicity it might be best to just use a cross-platform GUI system (either the GTK or KDE code) on Win32 instead of adding yet another gui framework to support. I don't know how badly it would impact the installer though.

[Richard42]

BTW, the port should allow us to merge into the latest version so that we will always be current with updates.

This depends on how the port is built. If it's written in a way which clutters up the common code with #ifdef WIN32s then it's going to live in its own branch and someone will be responsible for merging patches back and forth. If the changes are clean then I'll merge it into the trunk. If it the Win32 port adds a new Win32 GUI, then someone will have to keep the GUI code up to date as features are changed and added. But if it's written to use one of the pre-existing platform-independent GUI libraries, then it may be able to be fully integrated with the existing software, with very little maintenance required as we go forward..

[nmn]

If it's written in a way which clutters up the common code with #ifdef WIN32s then it's going to live in its own branch and someone will be responsible for merging patches back and forth. If the changes are clean then I'll merge it into the trunk.

It should be clean enough, there are a few ifdefs but it uses another macro that is defined by the CFLAGS in a seperate file. The reason is Cygwin may allow using the POSIX-like interface from inside of Windows. I had to split main.c, main.h, plugin.c, plugin.h, volume.c, and volume.h. Most of main.c and main.h are intact in the main/ directory but the remaining non-platform independent parts are seperated, and plugin.c plugin.h, volume.c, and volume.h are completely split.

The initial crude port was not good enough, So I went toward this idea.

[sultanoswing]

A tad off topic, but as a linux fan, it tickles me pink to see discussions hoping software will be ported to windows, rather than from it. Welcome to the future, people

[mudlord]

but as a linux fan, it tickles me pink to see discussions hoping software will be ported to windows, rather than from it. Welcome to the future, people

And way to show GNU zealotry there....>.>

Sheesh.

This is EXACTLY whats turning me off from using Linux altogether, is people like you.

[Slougi]

And way to show GNU zealotry there....>.>

Sheesh.

This is EXACTLY whats turning me off from using Linux altogether, is people like you.

Huh? I don't see the zealotry.



Anyway, I hacked on this a few days back. The KDE interface compiles fine, the core does need some work. So, if you can land the core changes we might get mupen64plus feat. KDE gui on windows I don't know how easy deployment currently is though.