How to: Compile x64 Dolphin with VC++2008 Express

[WhiteZero]

(12-07-2009, 01:28 AM)WhiteZero Wrote: Is there any reason I should be doing "Rebuild" instead of just "Build" everytime? I've had no problem just using Build for my revisions.
I know Rebuild completely redoes all the code, instead of just checking for changes like Build does. So if I should do Rebuild each time, would I be safe doing Rebuild for my 64bit and 32bit builds, then afterwards save time by just doing Build for the JITIL versions?

In other words, do I need to waste my time waiting for a Rebuild or can I just do Build and be safe?

Still looking for some input on my above post. Thanks!

[James333]

I said that because I have errors while compiling if I don't rebuild ( but now I have separated folders for my 32 and 64 bits builds of dolphin )

Yeah , I waste space , but theoretically I should be able to compile both versions of dolphin at the same time

[WhiteZero]

In all the builds I've made so far, I've never got an Error while compiling. So I guess I should be safe just doing Build.

EDIT: Nevermind. My last few builds have failed to update the Dolphin.exe to the new revision. Maybe it is actually updated but at least it says its still an older version. Oddly enough, the JITIL version, DolphinIL.exe does show as updated.

Weird... Guess I'll be Rebuilding from now on.

[WhiteZero]

I would like to warn people who use this guide (as awesome as it is).
If you ever intend to switch from Express to Professional (full version) and are doing 64bit compiles, and you followed the registry edits to make 64bit work in Express, your going to have a bit of a hard time changing to Professional.

Before installing VS Pro, your going to need to totally uninstall Express and delete the Visual Studio 9 registry section. After that, you can install VS Pro with working 64bit components.

[aeridus]

Thanks for the detailed tutorial! I thought I had everything set up properly, but it turns out that you really do need to select all options in the SDK installer. The last option is unselected by default and it didn't look terribly useful to me at the time.

[Morvie]

How do I compile OpenCl?
I have newest Stream SDK installed and have set the directories of include and library files in Visual Studio.

Is the wiki outdated ?
it says:
In Core/Common/Src/OpenCL.h, turn the "#if 0" to "#if 1"
I cannt find that line.

Is OpenCL used by default if i have Stream SDK or do i still need to change a file ?

[James333]

(12-23-2009, 09:23 PM)Morvie Wrote: How do I compile OpenCl?
I have newest Stream SDK installed and have set the directories of include and library files in Visual Studio.

Is the wiki outdated ?
it says:
In Core/Common/Src/OpenCL.h, turn the "#if 0" to "#if 1"
I cannt find that line.

Is OpenCL used by default if i have Stream SDK or do i still need to change a file ?

It's ... here

Quote:#ifndef __OPENCL_H__
#define __OPENCL_H__

#include "Common.h"
// Change to #if 1 if you want to test OpenCL (and you have it) on Windows
#if 0 <------------THERE !

[Morvie]

Thx, Got it now.

I didnt see the forest for the trees.

[Jefferson]

Mm...I have a question.
When you run the web installer. Are necessary all that things that weight more than 1 GB? O.o. Or only are necessary the libraries and tools?

[CacoFFF]

(01-12-2010, 02:58 AM)Jefferson Wrote: Mm...I have a question.
When you run the web installer. Are necessary all that things that weight more than 1 GB? O.o. Or only are necessary the libraries and tools?

Check Windows Headers and Libraries.
Check Visual C++ Compilers
Check Windows Development Tools

I did that myself and worked with Win2003 sdk, dunno what SDK you are running but you may try if you want.