Dolphin, the GameCube and Wii emulator - Forums

Hello all, I've been building the SVN source of Dolphin Emu for the past few days and have set up an archive of the builds. The newest build is always at the bottom

Now built with 64 and 32 bit love!

The 64bit binaries for use on the 64bit version of Ubuntu 10.04. I also tested that these builds DO work with the Ubuntu 10.10 Beta 2 also.

The i686 binaries for use on the 32bit version of Ubuntu 10.04. I haven't tested them on 10.10 beta 2.

Feel free to download and test, any questions can be asked here.

You can find my builds at
Dolphin Ubuntu daily builds - i686 and 64 bit

About time someone decided to do this. A lot of people will appreciate this, good job and welcome to the forums.

I updated my main development box to Ubuntu 10.10 beta 2 last night, the 64bit builds seems to work just fine under this new OS. No strange library incompatibilities or anything. So it should be happy gaming.

Current build as of 8:19am on Saturday Sept. 04, 2010 is 6172.

Have fun!

Now building i686 32 bit binaries too. See OP for address and info.

Good job man.

Working fine on openSUSE 11.3.
Although I'm using my own builds anyway it's nice to see that the builds aren't limited to Ubuntu

(09-05-2010, 09:47 PM)NeoBrain Wrote: [ -> ]Working fine on openSUSE 11.3.
Although I'm using my own builds anyway it's nice to see that the builds aren't limited to Ubuntu

Awesome, thanks for testing my build on OpenSuse. I don't blame ya for running your own build, it's so easy to make. The only thing I don't like about building it myself is sludging up my system with all the -dev packages. That's why I have 2 virtual machines (32 and 64 bit Ubuntu) for building them (virtualbox rocks, btw). It keeps my main OS slim and tidy.

Quick question, please, are there any compile time switches to build optimized builds. Like for the various SSE implementations. I see all kinda of Windows optimized builds but no documentation on doing it for linux.

Optimized builds would need the Intel C++ compiler which is why there is only Windows builds atm. Visual Studio doesn't support anything more than SSE2 or SSE3 compile time optimizations so I would expect that other compilers don't support SSSE3 and SSE4 optimizations.

As far as I can see, there's no simple option for scons to do this...
Try adding this line at the beginning of the SConstruct file in the main directory (parent dir of Externals, Source, etc):
In place of SOMEFLAGS, use any combination of these flags: (sse and sse2 are enabled by default IIRC)
Source: http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html not sure if those flags will work for icc as well. (Shouldn't be an issue for you )

Anyway, you need to the C prepocessor define _M_SSE as well to actually claim full SSEx.x-enabled builds... couldn't figure out how to do this with scons, just adding -D_M_SSE=0x401 yielded tons of warnings >_>

---

(09-06-2010, 01:43 AM)Xtreme2damax Wrote: [ -> ]Optimized builds would need the Intel C++ compiler which is why there is only Windows builds atm. Visual Studio doesn't support anything more than SSE2 or SSE3 compile time optimizations so I would expect that other compilers don't support SSSE3 and SSE4 optimizations.

huh? GCC does support optimization for about all processor extensions available...

Huh, then how come VS2008 doesn't?

I'm referring to compile time optimizations such as what ICC does, all compilers including VS2008 support hand coded SSSE3 and SSE4 optimizations. Switching on a flag with other compilers isn't going to do much unless hand coded optimizations have been implemented. That's the good thing about ICC, optimizing for SSSE3 and SSE4 to increase performance without the need to implement hand coded SSSE3 and SSE4 optimizations. There is only one drawback to SSSE3 and SSE4 optimizations with ICC, that hand coded optimizations will always be more efficient and give better performance.

Now perhaps if the developers worked on fully optimizing the plugins, videocommon and some of the functions for SSSE3 and SSE4 that would negate the need to use ICC for optimized builds.