Windows - Compile Guide and Support
Yes, rama, first thing in results I googled was this article. Unfortunately, it didn't really work, I've got 64 link and missing headers errors. One cup of good coffee was sacrificed to fix that manually for each plugin.

It was really good coffee.
Reply

Sponsored links

Get a refund.
[Image: newsig.jpg]
Reply
(04-14-2013, 01:18 AM)rama Wrote: Kein:
http://takinginitiative.net/2010/07/02/s...udio-2010/

This is how everyone I know does it.

Yup, globalness ftw!
[Image: nbKSK.jpg]
Reply
Hi everyone

Not sure this is the right place to post but I'll go anyway.
Out of curiosity, I tried to compile the Windows version of pcsx2, and found quite complex to setup.
Then I realized the Linux version was using CMake.
So, why isn't the windows version using CMake too ?
That would simplify things like configuring the paths for DirextX, CG, etc.

Also, I had to fix some stuff manually to be able to compile with VS2010 Express (lack of MFC in this one, lack of solution folder support)
Since the express version is free and anybody can use it, why is pcsx2 focusing on the 'regular' VS2010 ?
Anything specifically needed in that one ?

Thanks
Reply
Pcsx2 works fine with vs2010 express, you just need to set it up properly
[Image: ref-sig-anim.gif]

Reply
i was trying to compile gsdx and..
it is normal that there's a
Code:
$VTUNE_AMPLIFIER_XE_2011_DIR
variable in the compiling script?
Reply
Has anyone compiled a build on vs2013 yet? Just curious.

I'm not home until tommorow, I've not downloaded 2013 yet to check it out.
Reply
I got vs2013, but haven't had chance to try it myself either. Im suspecting the VS2012 project will convert quite happily and compile, lord knows if there are any speed changes or bugs mind ;p
[Image: ref-sig-anim.gif]

Reply
Edit: nvm, sorted it. (forgot to update this to say so)

I don't suppose anyone else has gotten this MFC linker error when building with vs2013 express? I probably have some root address in arseways tbh.

Code:
error MSB8031: Building an MFC project for a non-Unicode character set is deprecated. You must change the project property to Unicode or download an additional library. See http://go.microsoft.com/fwlink/p/?LinkId=286820 for more information.

I'm near certain I've dealt with this error before, but I can't bloody remember what I did to resolve it Tongue
Reply
(11-29-2013, 09:44 PM)Asmodean Wrote: Edit: nvm, sorted it. (forgot to update this to say so)

I don't suppose anyone else has gotten this MFC linker error when building with vs2013 express? I probably have some root address in arseways tbh.

Code:
error MSB8031: Building an MFC project for a non-Unicode character set is deprecated. You must change the project property to Unicode or download an additional library. See http://go.microsoft.com/fwlink/p/?LinkId=286820 for more information.

I'm near certain I've dealt with this error before, but I can't bloody remember what I did to resolve it Tongue

I just built on VS 2013 Ultimate trial. I got that error, and solved it with this:

http://search.microsoft.com/en-US/Downlo...=sp&q=mbcs

I'm not sure if that will work for express, but that's what I did.

Edit: Saw your edit, but leaving this up for anyone that cares lol
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply




Users browsing this thread: 1 Guest(s)