octo/yuzu-mainline
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
927 Commits 1 Branch 1 Tag 106 MiB
C++ 65.1%
cpp 30.6%
Kotlin 2.7%
CMake 0.7%
GLSL 0.3%
Other 0.5%
3e09c07378
Go to file
bunnei 3e09c07378 FS_User: Support FileSye::Path in a more generic way. 
added a todo to kernel archive
2014-11-17 22:18:58 -05:00
externals Added configuration file system. 2014-10-07 15:09:37 -07:00
src FS_User: Support FileSye::Path in a more generic way. 2014-11-17 22:18:58 -05:00
.gitignore Add a Doxygen configuration file to generate source docs 2014-10-26 16:14:46 -02:00
.gitmodules Added configuration file system. 2014-10-07 15:09:37 -07:00
.travis-build.sh Set Qt5_DIR in Travis to allow cmake to find Qt5 libraries. 2014-11-15 12:38:49 -08:00
.travis-deps.sh CMake cleanup 2014-09-01 18:06:30 -03:00
.travis.yml Travis: Added OSX, use default compilers, moved cmds into own scripts 2014-06-17 22:57:15 -07:00
CMakeLists.txt Added configuration file system. 2014-10-07 15:09:37 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-06-12 06:10:46 -04:00
doc-icon.png Add a Doxygen configuration file to generate source docs 2014-10-26 16:14:46 -02:00
Doxyfile Add a Doxygen configuration file to generate source docs 2014-10-26 16:14:46 -02:00
license.txt added license txt file 2014-04-08 19:03:00 -04:00
README.md Update README.md to correct OS X typo 2014-08-25 19:08:25 -04:00

README.md

citra emulator

Travis CI Build Status

An experimental open-source Nintendo 3DS emulator/debugger written in C++. Citra is written with portability in mind, with builds actively maintained for Windows, Linux and OS X. At this time, it only emulates a subset of 3DS hardware, and therefore is generally 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