9717e19be2
* Update sceNpTrophy.cpp * Revert "Update sceNpTrophy.cpp" * Update sceNpTrophy.cpp * Update sceNpTrophy.cpp |
||
---|---|---|
.github | ||
.travis | ||
3rdparty | ||
asmjit@673dcefaa0 | ||
asmjitsrc | ||
bin | ||
llvm@5c906fd169 | ||
llvm_build | ||
rpcs3 | ||
Utilities | ||
Vulkan | ||
.clang-format | ||
.editorconfig | ||
.gitignore | ||
.gitmodules | ||
.mention-bot | ||
.travis.yml | ||
appveyor.yml | ||
CMakeLists.txt | ||
git-clang-format | ||
LICENSE | ||
pre-commit.readme | ||
README.md | ||
rpcs3_debug.props | ||
rpcs3_default.props | ||
rpcs3_llvm.props | ||
rpcs3_memleak.props | ||
rpcs3_release.props | ||
rpcs3.sln | ||
usertype.dat |
RPCS3
The world's first free and open-source PlayStation 3 emulator/debugger, written in C++ for Windows and Linux.
You can find some basic information on our website. Game info is being populated on the Wiki. For discussion about this emulator, PS3 emulation, and game compatibility reports, please visit our forums and our Discord server.
Support Lead Developers Nekotekina and kd-11 on Patreon
Contributing
If you want to help the project but do not code, the best way to help out is to test games and make bug reports. See:
If you want to contribute as a developer, please take a look at the following pages:
You should also contact any of the developers in the forums or in the Discord server to learn more about the current state of the emulator.
Dependencies
Windows
- Visual Studio 2017
- Visual C++ Redistributable Packages for Visual Studio 2017
- CMake 3.8.2+ (add to PATH)
- Python 3.3+ (add to PATH)
- Vulkan SDK (See "Install the SDK" here)
- Qt 5.10+ (Avoid 5.11.1, due to a bug)
Either add the QTDIR
environment variable, e.g. <QtInstallFolder>\5.11.2\msvc2017_64\
, or use the Visual Studio Qt Plugin
Linux
- Qt 5.10+ (Avoid 5.11.1, due to a bug)
- GCC 7.3+ or Clang 5.0+
- CMake 3.8.2+
- Debian & Ubuntu:
sudo apt-get install cmake build-essential libasound2-dev libpulse-dev libopenal-dev libglew-dev zlib1g-dev libedit-dev libvulkan-dev libudev-dev git qt5-default libevdev-dev
- Arch:
sudo pacman -S glew openal cmake vulkan-validation-layers qt5-base
- Fedora:
sudo dnf install alsa-lib-devel cmake glew glew-devel libatomic libevdev-devel libudev-devel openal-devel qt5-devel vulkan-devel
- OpenSUSE:
sudo zypper install git cmake libasound2 libpulse-devel openal-soft-devel glew-devel zlib-devel libedit-devel vulkan-devel libudev-devel libqt5-qtbase-devel libevdev-devel
If you have an NVIDIA GPU, you may need to install the libglvnd package.
Building
Only Windows and Linux are officially supported for building. However, various other platforms are capable of building RPCS3. Other instructions may be found here.
Clone and initialize the repository:
git clone https://github.com/RPCS3/rpcs3.git
cd rpcs3/
git submodule update --init
Windows
Configuring the Qt plugin (if used)
- Go to the Qt5 menu and edit Qt5 options.
- Add the path to your Qt installation with compiler e.g.
<QtInstallFolder>\5.11.2\msvc2017_64
. - While selecting the rpcs3qt project, go to Qt5->Project Setting and select the version you added.
Building the projects
Open rpcs3.sln
. The recommended build configuration is Release - LLVM
for all purposes.
You may want to download precompiled LLVM libs 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
Linux
While still in the project root:
cd .. && mkdir rpcs3_build && cd rpcs3_build
cmake ../rpcs3/ && make GitVersion && make
- Run RPCS3 with
./bin/rpcs3
When using GDB, configure it to ignore SIGSEGV signal (handle SIGSEGV nostop noprint
).
If desired, use the various build options in CMakeLists.
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.