DaedalusX64: a Nintendo 64 emulator that still builds for handhelds
The Nintendo 64 Emulator itself
At a glance
- What is it?
- DaedalusX64 runs Nintendo 64 software on PSP, 3DS, Vita, Linux, macOS and Windows from one C++ codebase, with a portable build script that detects the host OS. The README is candid about its gaps: no big endian support, a broken Windows build, and native Apple Silicon only from source.
- Who is it for?
- DaedalusX64 fits a developer who wants to read or contribute to a real console emulator that still targets handheld platforms others have dropped, and who can supply their own game images and work around the missing Windows build. It does not fit someone who wants a polished, prebuilt binary on every platform, since the Windows build is broken and the Apple Silicon build is source only and slow.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
One C++ codebase across six platforms
DaedalusX64 is a Nintendo 64 emulator for PSP, 3DS, Vita, Linux, macOS and Windows. The multi-platform reach is unusual for an emulator of this age, and it is the reason the project is still worth reading. The stated feature list is short and claims fast emulation, high compatibility, support for those platforms, and active support and updates. The last of those is worth testing against the record, because the tagged releases are old, with 1.1.8 from 2019 and 1.1.7 from March of the same year, while the last push to the repository was on 2026-10-18. The source is C++ and the build is CMake based, with a top-level CMakeLists.txt, an Options.cmake and separate Source, Data, Tools and .vscode directories. The Data and Tools directories are what distinguish an emulator project from an ordinary application, since they hold the assets the emulator itself needs.
The one architecture gap is big endian
The README has a section on things that do not work right now, and it contains a single item: big endian is unsupported, so there are no PowerPC builds at the moment. That is a structural limitation rather than a missing feature, since the Nintendo 64's processor is a MIPS big endian design, and running that code on a little endian host is the emulator's central problem. The list of supported platforms is all little endian hardware, so the project works around the mismatch in software. The credits list shows how the work was distributed over the years, with named contributors for the 3DS support and ARM dynamic recompilation, for the PS Vita and ARM contributions, for compilation improvements and optimizations, and for wiki maintenance and continuous testing.
The build script detects your OS, which is the main convenience
Building on Posix systems is two steps. You clone the repository and then run the build script, which auto detects the OS you are on.
2) ./build_daedalus.sh (This will auto detect the OS you are on)Posix systems additionally require glew and SDL2 on top of the libraries every version needs, which are zlib, libpng and minizip. For PSP the route is different. You fetch the latest PSP Toolchain from the pspdev project and install the required libraries, then run the same script with the PSP argument, and CMake does the rest.
Run ./build_daedalus.sh PSP and CMake will do the required fun stuff :)The presence of a single script that dispatches on the target is what keeps a six-platform project maintainable. The repository also has build_cia.sh for the 3DS homebrew format and build_daedalus.bat for Windows, alongside the shell script.
Running it, and the Apple Silicon gap
For macOS and Linux you need the same prerequisites, libpng, zlib, minizip, glew and SDL2, installed through a package manager, and then you execute the emulator with the path to a ROM as the argument.
Execute the emulator ./daedalus 'Path to Rom' For PSP there is an extra manual step, copying the entire DaedalusX64 folder onto the Memory Stick and putting it in the PSP/Game directory. On Apple Silicon there is no native GitHub build, but the README says it compiles fine and works, just a bit slow as expected, which is a reasonable outcome for a translated MIPS workload on a CPU that does not have the hardware support. The Windows situation is worse, because the README states plainly that the Windows build is broken at the moment, with the Visual Studio instructions given as Clone and open the repo in Visual studio 2019, then Build All.
CI nightlies exist, and the README warns about them
The CI section is short and has a caveat attached. DaedalusX64 has CI, and you can get the latest nightlies from the Actions tab, but the README warns that these builds are sporatic at times. The official distribution channel is the releases page, with the instruction to download the latest release for your platform, and a joking alternative for people who want the newest code, using the latest builds in the GitHub Action section. The project's own guidance for finding out how well a specific game runs is its wiki, which the README describes as actively maintained, and it asks users to submit reports for games that have not already been listed. That community compatibility data is the more valuable artefact for most people, since emulator performance varies per title.
GPL-2.0, and a project that has outlived its release tags
The licence is GPL-2.0, which is the usual choice for emulators and carries the usual obligations if you redistribute a build. The more interesting point is the gap between the release tags and the current work. The listed releases are 1.1.8 from 2019 and 1.1.7 from earlier that year, yet the last push was on 2026-10-18 and the README claims active support and updates, with a Discord community for news. The practical reading is that most of the work since the last tag lives on the default branch and reaches users through CI nightlies rather than through a versioned release. For someone evaluating the project, that means you should read the recent commits rather than trust the version number, and for someone contributing it means the wiki, the Discord and the issue tracker are where the project actually lives. The credits section is also unusually long, and includes an explicit thank you to a tester for continuous testing over the duration of DaedalusX64, which tells you how much of the work is verification.
Editorial conclusion
DaedalusX64 fits a developer who wants to read or contribute to a real console emulator that still targets handheld platforms others have dropped, and who can supply their own game images and work around the missing Windows build. It does not fit someone who wants a polished, prebuilt binary on every platform, since the Windows build is broken and the Apple Silicon build is source only and slow. Verify first which platform build you actually need, check the wiki compatibility list for the games you care about, and read the build script before you start, because the PSP path needs its own toolchain and the Posix path needs glew and SDL2.
Frequently asked questions
Which platforms does DaedalusX64 run on?
PSP, 3DS, Vita, Linux, macOS and Windows. The README also states that big endian is not supported, so there are no PowerPC builds, and that the Windows build is currently broken while the native Apple Silicon build is not available from GitHub but compiles and runs from source.
How do I build DaedalusX64 on Linux or macOS?
Clone the repository and run the build script, which auto detects the OS you are on. You need zlib, libpng and minizip for all versions, and glew and SDL2 additionally on Posix systems. The PSP build needs the pspdev toolchain and the same script with the PSP argument.
How do I run a game with DaedalusX64?
On macOS and Linux you execute the emulator with the path to the ROM as an argument, for example ./daedalus with the ROM path. On PSP you copy the entire DaedalusX64 folder to the Memory Stick and place it in the PSP/Game directory.
Where can I find compatibility information for DaedalusX64?
The README points to the project's wiki as the actively maintained place for compatibility, optimal settings and more, and asks users to submit reports for games that are not already listed. There is also a Discord server for news.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/daedalusx64-daedalus)Was this useful?