Guide:- Compiling PPSSPP on Windows for Dummies (updated for MSVC 2013)

[xsacha]

For anyone who is interested, I compiled the Qt version of PPSSPP for Windows:
https://mega.co.nz/#!S5ATxDhS!YHIaiHZ6oD...87pdXcr4rs
Included the Qt dlls as well.

[bhavin192]

Somebody please help me in setting system environment "GIT"
git is installed in C:\Programe Files (x86)\git
I have set it like in image

but still git-version-gen.cmd giving same error
git not on path.....

[TheDax]

Does it work if you put it under system variables? Have you tried rebooting your computer after adding it to your local variables?


Maybe just add it directly to your system's PATH instead, if it's not in there. That's where it put it on my PC..

[bhavin192]

(12-19-2013 03:57 PM)TheDax Wrote:  Does it work if you put it under system variables? Have you tried rebooting your computer after adding it to your local variables?


Maybe just add it directly to your system's PATH instead, if it's not in there. That's where it put it on my PC..

Tried putting in both and also restart not worked (I am on win 8.1)

It should be program files (x86) or just program files but I dont think they are same

[TheDax]

They're not. On a 64-bit OS, Program Files is for 64-bit programs (though technically you can put anything in there), and Program Files (x86) is for 32-bit programs.

If it didn't work after adding it to your PATH, then I dunno what else to say. What does your PATH look like?

[solarmystic]

@bhavin192

As TheDax has mentioned, you have to place it under the PATH variable located under the System Variables category and ONLY in that location. Adding multiple entries under other variable names will not work. E.g. the GIT variable you added earlier on.

As an example, I installed git to D:\Apps\Git so I added D:\Apps\Git\cmd to the PATH variable under System Variables as follows:-

[bhavin192]

@solarmystic
still having same error also tried disabling user account control

[NgJinXiang14]

how to patch thing into ppsspp and ANGLE using git-apply?
http://forums.ppsspp.org/showthread.php?tid=2399&page=7

[HolyBash]

Is this the same with windows 64bit if not, a tutorial would be alot much much better.

[solarmystic]

Updated the guide to reflect the new requirement of Microsoft Visual Studio 2013 to compile all Windows builds starting from v0.9.6-804-g9c41246 onwards.

The overall procedure for the compiling guide has been simplified thanks to this compiler update, with the following major changes:-

1. Users do not have have to download and install Windows 7.1 SDK anymore to compile 64bit builds. All versions of Visual Studio 2013 (including Microsoft Visual Studio Express 2013 used for this guide since it's freely available from Microsoft) can compile 64bit executables; no additional components are required. Users who followed this guide previously may uninstall both MSVC 2010 and 7.1 SDK from their systems if they are not developing/compiling any other older program to free up some HDD space.

2. As a result of (1), the compiling procedure in Visual Studio itself is now streamlined for both 32bit and 64bit builds. No more platform toolset changes are required for the native, PPSSPPHeadless, UnitTest and zlib projects; in fact the only change one is required to make for 64bit builds is to set the drop down menus in the Configuration Manager mentioned in the guide to Release and x64 for Active Solution Configuration and Active Solution Platform respectively, as shown in the guide.

3. The DX SDK is still required for running/compiling Debug and debugging Debug builds (even with the dxsdk submodule) unfortunately, so I've kept that prerequisite in the procedure.

There are many downsides to this (long awaited) upgrade as compared to MSVC 2010, however:-

1. The minimum OS requirement to compile PPSSPP is now Windows 7 SP1. If you've been compiling PPSSPP on your Windows XP or Vista (god forbid) machine, you are out of luck. Perhaps it is time for an upgrade?

2. Getting the all in one ISO for Visual Studio Express 2013 (used for offline installations and convenience) is a pain in the behind and not as straightforward as it used to be for 2010. Users will have to register a Microsoft account (if you don't already have one, it's the same credentials you'd use to login to your Outlook/Hotmail/etc accounts) and use it to login to Microsoft's proprietary page in order to get the direct download link to the ISO (redirected from the main VS page). On the upside, installation for MSVC 2013 is pretty damn straightforward and everything that is required will be installed and updated automatically. This simplicity does come at at price, which brings us to the following point.

3. Increased HDD space requirement and component bloat. A whooping 5-6 GB is required since the installer will forcibly install every single component (many of which are not actually required to compile PPSSPP) and none are optional. That may not seem like much, but smallish SSD users should be wary of this, since the primary OS drive will be used to house most of it, regardless of the location you chose to install the software in the place.

Case in point (look at all that unnecessary SQL server crap!):-



4. Internet Explorer 10 (at a minimum) is now required. If you're like me, refused to touch that POS software (Firefox/Palemoon/etc for the win) and had it removed from the Windows Component store during a fresh Windows 7 install, you'll be disappointed to know that it is mandatory to have IE10 before even installing MSVC 2013.

5. Remember the Microsoft Account that you used to get the 2013 ISO download? Well guess what, you'll have to use it to eventually register the software online to extend the usage period of Express 2013 which will go into lockdown (it happened to me after a few months of unregistered usage) if you don't. Ah, the always online digital future, I love it, don't you? Fortunately, you only have to do this once and then you can stay offline (like any sane person would) and block that POS Microsoft sign in functionality for eternity which has no place on the desktop for offline based applications. Also helps to disable those obnoxious dynamic download updates too!

All the bits that relate to the git, and github procedure remain exactly the same after 2013. No changes there.

[Raimoo]

So.. compling 32 bits will be easier with VS 2013 right?

[solarmystic]

(02-09-2014 12:37 AM)Raimoo Wrote:  So.. compling 32 bits will be easier with VS 2013 right?

Pretty much every platform is simplified now. That is the biggest benefit from switching over to MSVC 2013. Just read the guide on the first page, it's changed quite a bit now.

[Oblivion]

@solarmystic
I want to revert changes made by this commit (merge) (causes Dissidia 012 and some other games' speed to drop 30%) and this commit (merge) (causes Dissidia 012 to have a red tint on cutscenes with a light background) and keep everything else intact. Is that possible with git or will I have to make the changes myself?

[solarmystic]

(02-10-2014 07:33 PM)Oblivion Wrote:  @solarmystic
I want to revert changes made by this commit (merge) (causes Dissidia 012 and some other games' speed to drop 30%) and this commit (merge) (causes Dissidia 012 to have a red tint on cutscenes with a light background) and keep everything else intact. Is that possible with git or will I have to make the changes myself?

It is possible to do so.

The proscribed command for those two cases (assuming you're up to date using a git pull and you have NO current modifications to your working ppsspp directory that contains all the source files) would be:-

Code:

git revert --no-edit 2f7243b 09f1c79 60cf5df b48de95 c6dc6b4 9cfb864

Each set of numbers represents the first 7 digits of the SHA-1 commit id for each commit that you wish to revert. Note that we're not reverting the commits that merge them to master, but we're reverting the ones added in by the original authors of the commits themselves.

The commit by Bigpet which introduced the red tint on cutscenes is originally

Code:

2f7243b

There are 5 seperate commits by [Unknown] that make up his pull request which got merged to master and they are

Code:

09f1c79 60cf5df b48de95 c6dc6b4 9cfb864

You can get those details on the "Files" tab of the original pull request for each commit.

If you ever decide to change your mind on the revert and restore the original master back to the way it was, the command as always, is,

Code:

git reset --hard <current master commit id>

since a revert in itself is considered an additional commit that you're pushing to your own repository. Thus resetting the tree would be the easiest way to go back to the original path.

[Oblivion]

@solarmystic
Thank you. I didn't have time to reply last week.

Initially, I tried to revert the merge. That did not work out well. I had to choose a parent but I did not know which one to choose.

The command to revert the commit is correct but I had to make a modification to your command pertaining to the order of the commits (SHA-1 hashes) shown in your command.

Your command:

(02-10-2014 09:56 PM)solarmystic Wrote:  

Code:

git revert --no-edit 2f7243b 09f1c79 60cf5df b48de95 c6dc6b4 9cfb864

When I enter this command in the terminal, I received an "error: could not revert b48de95...duplicate framebuffers textured onto themselves."

I decided to restore to the original master and reverse the order of the commits ((SHA-1 hashes) by [Unknown]) shown in your command. This modification allow Git Bash to revert the commits successfully.

Code:

git revert --no-edit 2f7243b 9cfb864 c6dc6b4 b48de95 60cf5df 09f1c79

Also, I ran into a problem with running this command. (Unfortunately, reinstalling git does not fix the problem) Other commands work fine except for this one:

Code:

git submodule update --init

The command occasionally hangs or freezes the Git Bash terminal so I had to follow FAQ Q7 for the other half of the submodules.

(08-01-2013 05:57 PM)solarmystic Wrote:  7. I've a totally offline PC but have access to another PC with Internet that I can use to get the source files. How do I compile PPSSPP on my system?
(question courtesy of arg274 and answer credited to Daxtsu)

Refer to this post for the answer.

(08-13-2013 12:54 PM)daxtsu Wrote:  If you want to do an offline build, you're better off downloading the latest master zip file, followed by native, ffmpeg, and lang, then extracting those latter 3 in the master's native, ffmpeg and lang folders, then compiling. You can skip lang and ffmpeg most of the time if you already have them; they're not updated often..

Not much point going through the whole git thing if you can't update to begin with.

Also, adjust your expectations accordingly, since without the fine control with individual commits offered by git bash that requires an online connection, you'll have redownload the bulk files everyday from your PC with the Internet connection. I highly recommend that you actually use the PC with the persistent Internet connection to compile PPSSPP.

For this part you should also include the dx9sdk (minidx9) submodule if you do not want to run into an error while compiling under MSVC 2013.