Windows - Compile Guide and Support

[pcsx2fan]

Ah, I just compiled pcsx2-r4423.exe that no longer crash itself after clicking Config -> Emulation Settings.

The same problem here for ZZogl.

[Selvec]

The guide in the first post that's meant to have a link up to VS2008 is linking up to VS2010 thanks to Microsoft. Might want to give that a change.

Is there a smaller compiler then the 3gig VS2008 Pro 90 day Trial? As due to data caps in my country, that's a massive download.

[refraction]

Looks like Microsoft have retired the 2008 express edition, which means the guide linked in the first post will have to be rewritten to just be visual studio 2010

[Selvec]

Looks like Microsoft have retired the 2008 express edition, which means the guide linked in the first post will have to be rewritten to just be visual studio 2010

And like the capped crusader from the shadows he swoops in to save Gothem once more.

http://www.9down.com/Visual-Studio-2008-...nal-19735/

Now I think that's only the iso, so it should all be trials, meaning it's legal.

Edit:

By the way. I noticed that the guide also makes no mention of the difference in pathways from XP to Vista/Win7 64bit when changing the VB directories. This may need a change also.

Example:
XP: $(ProgramFiles)\NVIDIA Corporation\Cg\lib
Vista/Win7 64bit: $(ProgramFiles(x86))\NVIDIA Corporation\Cg\lib


Might be wrong there. But in Win7 64bit the program files for all software thats x86 gets installed in that folder.

[pcsx2fan]

I'm not sure if I set right Properties from TortoiseSVN for changes in r4488, please tell me if I am doing right or wrong.

Step 1
*I removed the screenshot it's no longer necessary*

Step 2
*I removed the screenshot it's no longer necessary*

[Bright-Warrior]

Hey guys,

I have a (for me ) strange and also annoying issue with compiling PCSX2 (r4513). I sure do not compile the emulator for the first time, I often did it on my old PC (successfully btw.). But it just fails on my new one and I'm pretty clueless about this.

The differences between the two PCs are that I'm now using Windows 7 64-bit instead of 32-bit and that, as a student, I now have access to Visual Studio 2008 Professional. I was using VS C++ Express on my old rig.

When the compilation fails, VS gives me the following error message:

Code:

12>Microsoft (R) Windows (R) Resource Compiler Version 6.0.5724.0
12>Copyright (C) Microsoft Corporation.  All rights reserved.
12>Verknüpfen...
12>x86emitter.lib(cpudetect.obj) : error LNK2001: Nicht aufgelöstes externes Symbol "___xgetbv".
12>C:\Users\[...]\Desktop\PCSX2 r4513\\bin\\pcsx2.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise.

Translated:

Code:

12>Microsoft (R) Windows (R) Resource Compiler Version 6.0.5724.0
12>Copyright (C) Microsoft Corporation.  All rights reserved.
12>Connecting...
12>x86emitter.lib(cpudetect.obj) : error LNK2001: Not solved external symbol "___xgetbv".
12>C:\Users\[...]\Desktop\PCSX2 r4513\\bin\\pcsx2.exe : fatal error LNK1120: 1 not solved external link.

I hope I translated that right, I have little understanding of what is happening there .

I also do have a suspect where the problem is: In the compilation guide in the part about configuring the build environment it says "Under the Win32 Platform, you need to add the following to Include files:[...]" and "Under the Win32 Platform, you need to add the following to Library files:[...]" and "Under the x64 Platform, I added the following for Library files:[...]". What of these things am I supposed to do on my 64-bit Windows? Or do I understand that wrong and "Win32 Platform" and "x64 Platform" are things that I have to select in this drop-down menu under the word "Platform" in the menu about "Projects and Solutions"? If so, I was just able to find Win32 Platform there. The other options are "Pocket PC 2003 (ARMV4)", "Smartphone 2003 (ARMV4)", "Windows Mobile 5.0 Pocket PC" and "Windows Mobile 5.0 Smartphone". No x64 present .

I hope you can help me.

Regards
Bright-Warrior

[Hungry Man]

GSDX won't work. Getting a dynamic library error.

*sigh* am I gonna have to start with vs2010?

[Shadow Lady]

When the compilation fails, VS gives me the following error message:

Code:

12>x86emitter.lib(cpudetect.obj) : error LNK2001: Not solved external symbol "___xgetbv".

You need to update your VS2008 to SP1 for that error.

[Bright-Warrior]

You need to update your VS2008 to SP1 for that error.

I already installed all updates available for VS (with the exception of SQL Server 2005 SP4, but I guess that's not the problem...) via Windows Update and the version number says "Version 3.5 SP1". I guess that means I also installed the Service Pack, doesn't it?

[Hungry Man]

Anyone know what the problem could be?

I've emptied out the pcsx2 folder and completely redownloaded everything so I assume the problem is that gsdx is currently broken or that VS2008 is messing up. I don't see any updates for it.