citra-emu
/
citra-canary
Archived
1
0
Fork 0
Code
This repository has been archived on 2024-03-23. You can view files and clone it, but cannot push or open issues or pull requests.
703 Commits 1 Branch 0 Tags 58 MiB
cpp 65.1%
C++ 30.5%
Kotlin 3.5%
CMake 0.6%
GLSL 0.2%
Go to file
bunnei fab2f28ea5 Merge pull request #73 from yuriks/remove-docs 
Remove documentation for external modules.
 		2014-08-23 22:12:59 -04:00
externals Remove documentation for external modules. 2014-08-23 11:48:58 -03:00
src Merge pull request #68 from archshift/readfile 2014-08-22 18:50:00 -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 Add Qt5 option. Use Qt5 by default. 2014-08-19 21:34:00 +10:00
.travis-deps.sh Add Qt5 option. Use Qt5 by default. 2014-08-19 21:34:00 +10:00
.travis.yml Travis: Added OSX, use default compilers, moved cmds into own scripts 2014-06-17 22:57:15 -07:00
CMakeLists.txt Add Qt5 option. Use Qt5 by default. 2014-08-19 21:34:00 +10:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-06-12 06:10:46 -04:00
README.md Added CONTRIBUTING.md with contents from Coding Style, updated README link 2014-06-12 06:10:45 -04:00
citra.sln added video_core as a dependencie for citra in build order 2014-04-06 16:57:09 -04:00
license.txt added license txt file 2014-04-08 19:03:00 -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