rpcs3/README.md

RPCS3

The world's first open-source PlayStation 3 emulator/debugger written in C++ for Windows and Linux.

You can find some basic information in our website. For discussion about this emulator and PS3 emulation please visit our forums and our Discord server.

Support Lead Developers Nekotekina and kd-11 on Patreon

Development

If you want to contribute please take a look at the Coding Style, Roadmap and Developer Information pages. You should as well contact any of the developers in the forums or in Discord in order to know more about the current situation of the emulator.

Dependencies

Windows

• Visual Studio 2015
• Visual C++ Redistributable Packages for Visual Studio 2015
• Cmake 3.1.0+ (required; add to PATH)
• Python 3.3+ (required; add to PATH)
• Qt 5.8+ (required; add QTDIR <QtInstallFolder>\5.8\msvc2015_64\ environment variable if you do not want to use the Visual Studio Qt Plugin)
• Visual Studio Qt Plugin (optional; see above)

Linux

• Qt 5.7+
• GCC 5.1+ or Clang 3.5.0+ (not GCC 6.1)
• Debian & Ubuntu: sudo apt-get install cmake build-essential libasound2-dev libopenal-dev libglew-dev zlib1g-dev libedit-dev libvulkan-dev libudev-dev git qt5-default
• Arch: sudo pacman -S glew openal cmake llvm qt5-base
• Fedora: sudo dnf install cmake qt5-devel vulkan-devel glew glew-devel If you have a NVIDIA GPU, you may need to install the libglvnd package.

MacOS

MacOS is not supported at this moment because it doesn't meet system requirements (OpenGL 4.3)

• Xcode 6+ (tested with Xcode 6.4)
• Install with Homebrew: brew install glew llvm qt cmake

Building on Windows:

To initialize the repository don't forget to execute git submodule update --init to pull the submodules.

Configuring Qt

If you're using Visual Studio 2017 without Qt plugin support (or simply dont want to use it):

1. Add QTDIR environment variable and set it to <QtInstallFolder>\5.8\msvc2015_64\
   

Open rpcs3.sln

If you wish to use the Visual Studio plugin for Qt:

1. Go to the Qt5 menu and edit Qt5 options. Add the path to your Qt installation with compiler e.g. C:\Qt\5.8\msvc2015_64.
   
2. While selecting the rpcs3qt project, go to Qt5->Project Setting and select the version you added.

Building the projects

You may want to download precompiled LLVM lib and extract to root rpcs3 folder (which contains rpcs3.sln), as well as download and extract additional libs to lib\%CONFIGURATION%-x64\ to speed up compilation time (unoptimised/debug libs are currently not available precompiled).

If you're not using precompiled libs, build the projects in __BUILD_BEFORE folder: right-click on every project > Build.

Build > Build Solution

Building on Linux & Mac OS:

1. git clone https://github.com/RPCS3/rpcs3.git
   
2. cd rpcs3/
   
3. git submodule update --init
   
4. cd ../ && mkdir rpcs3_build && cd rpcs3_build
5. cmake ../rpcs3/ && make GitVersion && make
   
6. Run RPCS3 with ./bin/rpcs3
   

If you are on MacOS and want to build with brew llvm and qt don't forget to add the following environment variables

• LLVM_DIR=/usr/local/opt/llvm/ (or wherever llvm was installed).
• Qt5_DIR=/usr/local/opt/qt/lib/cmake/Qt5 (or wherever qt was installed).

When using GDB, configure it to ignore SIGSEGV signal (handle SIGSEGV nostop noprint).

CMake Build Options (Linux & Mac OS)

• -DUSE_SYSTEM_LIBPNG=ON/OFF (default = OFF)
  Build against the shared libpng instead of using the builtin one. libpng 1.6+ highly recommended. Try this option if you get version conflict errors or only see black game icons.

• -DUSE_SYSTEM_FFMPEG=ON/OFF (default = OFF)
  Build against the shared ffmpeg libraries instead of using the builtin patched version. Try this if the builtin version breaks the OpenGL renderer for you.

• -DWITHOUT_LLVM=ON/OFF (default = OFF)
  This forces RPCS3 to build without LLVM, not recommended.

• -DWITH_GDB=ON/OFF (default = OFF)
  This Builds RPCS3 with support for debugging PS3 games using gdb.

• -DUSE_VULKAN=ON/OFF (default = ON)
  This builds RPCS3 with Vulkan support.

License

Most files are licensed under the terms of GNU GPLv2 License, see LICENSE file for details. Some files may be licensed differently, check appropriate file headers for details.