N-archive/citra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
439 commits 1 branch 0 tags 134 MiB
Find a file
bunnei 1c867b569d Kernel: Added real support for thread and event blocking 
- SVC: Added ExitThread support
- SVC: Added SignalEvent support
- Thread: Added WAITTYPE_EVENT for waiting threads for event signals
- Thread: Added support for blocking on other threads to finish (e.g. Thread::Join)
- Thread: Added debug function for printing current threads ready for execution
- Thread: Removed hack/broken thread ready state code from Kernel::Reschedule
- Mutex: Moved WaitCurrentThread from SVC to Mutex::WaitSynchronization
- Event: Added support for blocking threads on event signalling
2014-06-05 22:35:36 -04:00
externals fixes to scm_rev generation to make it conistent with windows build 2014-04-23 19:13:00 -07:00
src Kernel: Added real support for thread and event blocking 2014-06-05 22:35:36 -04:00
vsprops fixed VSProps for Qt DLL copy 2014-04-21 22:00:13 -04:00
.gitignore updated windows scm_rev code to use new style 2014-04-23 22:04:33 -04:00
.travis.yml Yet anothing missing dependency? libxcursor-dev 2014-04-25 22:04:18 -04:00
citra.sln added video_core as a dependencie for citra in build order 2014-04-06 16:57:09 -04:00
CMakeLists.txt Fixed CMake's import of GLFW. 2014-04-25 10:50:25 -04:00
license.txt added license txt file 2014-04-08 19:03:00 -04:00
README.md added FAQ link to README.md 2014-04-28 17:07:48 -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 Coding Style, 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