mirrors/yuzu
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
FUCK NINTENDO (x2)
734 commits 1 branch 0 tags 106 MiB
C++ 65.1%
cpp 30.6%
Kotlin 2.7%
CMake 0.7%
GLSL 0.3%
Other 0.5%
Find a file
bunnei 7122c46937 Merge pull request #81 from yuriks/downgrade-shader 
Downgrade GLSL version to 1.50 (compatible with GL 3.2)
2014-08-28 12:10:40 -04:00
externals Remove documentation for external modules. 2014-08-23 11:48:58 -03:00
src Downgrade GLSL version to 1.50 (compatible with GL 3.2) 2014-08-28 05:38:13 -03: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
citra.sln added video_core as a dependencie for citra in build order 2014-04-06 16:57:09 -04:00
CMakeLists.txt Pica: Add support for dumping textures. 2014-08-25 22:03:18 +02: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 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