Emulator

Using this ugly, ugly patch: http://paste2.org/p/161394, I got this:
http://paste2.org/p/161397. Help?

Issue 730 has been merged into this issue.

ok. The thing that's causing most of these problems is code that's in #ifdef _WIN32
blocks. I have tried commenting out #define _WIN32 from lines 73 and 115 of
platform.h, but that doesn't fix it. Any help?

Found out that I should be using #ifdef MINGW32 instead of something else. Now
fixing.

now using #ifdef MSVC, instead of #ifdef _WIN32.

So far, I've gotten to FileUtils.cpp. Here's a patch: http://paste2.org/p/162245

just so you know, even if you use the current patch, a compile with mingw will not
function correctly.
Take ABI.cpp for example, ignoring the arch by checking for the vs compiler only
avoids the compile error, does not port the code so that it compiles correctly.

commonfuncs changes it to use the slow generic implementation of swap16, I imagine
mingw has an equivalent function of _byteswap_ushort or bswap_16

ok then. how would I go about porting the code for the srch stuff? I'll see if I can
figure it out.

first I would check with nakeee, because the default install of gcc with mingw is
3.4.5, afaik for linux gcc 4.3.0 is required. an alpha version of gcc 4.3.0 is
available for mingw, but do we want to be using that to compile?
for the arch i believe just adding _M_IX86 as a define to the scons for windows

yes, it's better to use 4.3.0
I don't think it will get far with 3.4.5 (might be that some of the problems are
related to that).

I'm sure almost all of the problems are CAUSED by that. Now, I think the best way
would be to bundle a small version of gcc 4.3.x with dolphin, as long as it's small
(less than about 5mb). I'll try and configure it in scons, but it might be rather
complicated.

would it be better to use 4.3.0 or 4.3.3?

is anyone working on this still?

You might as well use TDM-GCC (http://www.tdragon.net/recentgcc/) instead of MinGW.
It officially supports GCC 4.4.1. I'm really looking forward for you to port Dolphin
to MinGW or TDM-GCC. Can't help much on that as I've been busy lately with other
projects, not to mention I would probably lack the knowledge to actually help XD In
any case, please consider using TDM-GCC. Cheers.

It shouldnt matter if its MingW, TDM-GCC, a random cygwin port or some other GCC
binary/clone/whatever for Win32, it only has to be configured for use.

@Issue: One big problem with the Win32 build is the lack of Externals building in the
current scons, like wx and other things that are available through on Linux and OSX. I tried to create a platform-specific scons for
Win32, but failed epicly. Maybe I'll do some more tests with it, but for now I'd
recommend sticking to Visual Studio (there are even tutorials out there on how to
build x86 and x64 with the free version Visual C++ Express).

From what I could tell, one of the issues with using MinGW is that GCC has been stuck
at version 3.4.5 for quite some time now (some few years, I think), and Dolphin, at
its current state, would possibly require GCC 4.3.0, at least (nakeee's words). On
TDM-GCC, GCC version 4.4.1 is claimed to be ready for production use. Hence my
suggestion.

if not i can provide a mingw with the gcc-4.4.3 compiler and builtin python with
scons (actually just uploaded the project to google code).

its not the everyday mingw by far mine uses the mingw64 api and headers but the 32
bit versions and despite the i686-pc-mingw32 tripple its not a crosscompiler (can be
used as one though).

the beast is 800 mb's though and includes an svn build of codeblocks and pretty much
any utility/library you could want but might take a while to download.
ftp://90.184.233.166:21/mingw.exe