octo/citra
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
citra-emu
1,054 Commits 52 Branches 0 Tags 63 MiB
cpp 65.2%
C++ 30.4%
Kotlin 3.5%
CMake 0.6%
GLSL 0.2%
55ce9aca71
Go to file
Tony Wasserka 55ce9aca71 citra-qt: Add pica framebuffer widget.
2014-12-09 16:37:34 +01:00
externals Added configuration file system. 2014-10-07 15:09:37 -07:00
src citra-qt: Add pica framebuffer widget. 2014-12-09 16:37:34 +01:00
.gitignore Update gitignore to exclude project/editor files 2014-11-18 15:16:19 -08: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
CMakeLists.txt CMake: Place all the built files in BUILD_DIR/bin/<Configuration> when compiling with MSVC 2014-12-01 18:48:27 -05:00
CONTRIBUTING.md Resolve doxycomment duplication debate 2014-12-04 04:47:52 -02: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
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