TechnoHector/suyu
2
1
Fork 0
forked from suyu/suyu
Code Pull requests Activity
Fork of Suyu for making my own implementations without affecting main project.
686 commits 18 branches 1 tag 270 MiB
C++ 64.2%
cpp 31.6%
Kotlin 2.6%
CMake 0.7%
GLSL 0.3%
Other 0.4%
Find a file
Lioncash ab4648d3ca Core: Use std::array for managing kernel object space 
These avoid relying on memset for clearing the arrays.
2014-08-19 00:32:48 -04:00
externals CMake Cleanup 2014-08-18 14:35:44 +10:00
src Core: Use std::array for managing kernel object space 2014-08-19 00:32:48 -04:00
vsprops citra_qt: Removed autogenerated files from repo and fixed build issues. 2014-06-22 16:37:07 -04:00
.gitignore citra_qt: Removed autogenerated files from repo and fixed build issues. 2014-06-22 16:37:07 -04:00
.travis-build.sh Travis: Added OSX, use default compilers, moved cmds into own scripts 2014-06-17 22:57:15 -07:00
.travis-deps.sh Travis: Added OSX, use default compilers, moved cmds into own scripts 2014-06-17 22:57:15 -07:00
.travis.yml Travis: Added OSX, use default compilers, moved cmds into own scripts 2014-06-17 22:57:15 -07:00
citra.sln added video_core as a dependencie for citra in build order 2014-04-06 16:57:09 -04:00
CMakeLists.txt CMake Cleanup 2014-08-18 14:35:44 +10:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-06-12 06:10:46 -04:00
license.txt added license txt file 2014-04-08 19:03:00 -04:00
README.md Added CONTRIBUTING.md with contents from Coding Style, updated README link 2014-06-12 06:10:45 -04:00

README.md

citra emulator

Travis CI Build Status

An experimental open-source Nintendo 3DS emulator/debugger written in C++. At this time, it only emulates a very small subset of 3DS hardware, and therefore is only useful for booting/debugging very simple homebrew demos. Citra is licensed under the GPLv2. Refer to the license.txt file included. Please read the FAQ before getting started with the project.

For development discussion, please join us @ #citra on freenode.

Development

If you want to contribute please take a took at the Contributor's Guide, Roadmap and Developer Information pages. You should as well contact any of the developers in the forum in order to know about the current state of the emulator.

Building