de6e324bdseparate emu thread10d3daf86Roms List improvements95d202f37Let's make the rom list process on a separate thread so the emulator doesnt take ages to load.fc306967fWow the ROM Header was just completely busted. Game list view works nowbad1691eefuck this shit2b59e5f46game list in progressd26417b83remappable inputs in progressac4af8106inpute72abc240update readme430139dc9Qt6 frontend3080d4d45Fix this small bug too08cd13b85Cop0 unused functions do not actually pose a threat (as per manual). They don't do anything, so shall we.61bb4fb44make idle loop detection a little more specific with where the load goesb037de4c3SAZDFsdff12e81e73eneed to figure out why n64-systemtest loops indefinitely at some address that appears to be valid (i think it's me not invalidating the cache properly)204f0e13bidle skipping seems to work!cb8bb634asdkfjlasdf58e5c89c1Fix compilation issue on my machine (no idea)24fb2898eattempting more serious idle skipping214719577Place rsp.Step inside cached interpreter. Gains about 3 more fpsbb97dcc23mmmmm920b77d38wjkhasdfjhkasdf430ccdab4it's a start...4f42a673aCached interpreter plays Mario 64. Start looking into RSP as wellc9a030787idle skipping works!5fbda03cenew idea366637abaIdle skipping... maybe?609fa2fb0Cache instructions implemented but broken lmao. Commented out for nowe140a6d12- Stop using inheritance for CPU, instead use composition. - Introduce KAIZEN_JIT_ENABLED optional define instead of relying on __aarch64__ and the like. - More cache work68e613057prep cache impl811b4d809fix clang formatfda755f7didkd5024ebbfsmall MI refactor in preparation of (eventually) implementing the RDRAM interface properly694b45341Merge commit '206dcdedf195fb320913584180edb12c7731e396' as 'external/SDL'206dcdedfSquashed 'external/SDL/' content from commit 4d17b99d0a4d16e1cb4need to update sdl848b19920Fix compilation errordb61b5299Merge commit 'e94a94559f28e49678fbcf72199a5258137b0fe9' as 'external/imgui'e94a94559Squashed 'external/imgui/' content from commit 02e9b8cac52edb3757need to update imguic1a705e86Emulate weird JALR behaviour4b4c32f4bFix exception for "unusable COP1" in 4 instructions i missed accidentally (again)df5828142Bug putting 0s in the log everywheref8b580048Make isviewer a sink to file8241e9735Fix exception for "unusable COP1" in 4 instructions i missed accidentallyb29715f20small changesd9a620bc1make use of my new small utility library0d1aa938eAdd 'external/ircolib/' from commit 'ce3cd726c8df8388d554abf8bb55d55020eb4450'e64eb40b3Fuck git git-subtree-dir: external/ircolib git-subtree-split:de6e324bde
4.6 KiB
Building Capstone
This guide describes how to build Capstone with CMake.
Build commands
Unix
cmake -B build -DCMAKE_BUILD_TYPE=Release # For debug build change "Release" to "Debug"
cmake --build build
cmake --install build --prefix "<install-prefix>"
To create rpm, debian and OSX packages, run the following
cmake -B build -DCMAKE_BUILD_TYPE=Release -DCAPSTONE_BUILD_SHARED_LIBS=1 -DCMAKE_INSTALL_PREFIX=/usr
cmake --build build
cd build
cpack -G DEB
cpack -G RPM
cpack -G DragNDrop
Windows
cmake.exe -B build
cmake.exe --build build --config Release # For debug build change "Release" to "Debug"
cmake.exe --install build
Tailor Capstone to your needs.
Enable and disable options in the "configure" step (first cmake command from above).
Options are added with -D<OPTION>=ON/OFF or -D<OPTION>=1/0
Exclude architecture modules
You can build Capstone with only the architectures you need. By default all are enabled.
CAPSTONE_ARCHITECTURE_DEFAULT: Whether all architectures are enabled by default.CAPSTONE_ARM_SUPPORT: Support ARM.CAPSTONE_AARCH64_SUPPORT: Support AARCH64.CAPSTONE_ALPHA_SUPPORT: Support Alpha.CAPSTONE_ARC_SUPPORT: Support ARC.CAPSTONE_HPPA_SUPPORT: Support HPPA.CAPSTONE_LOONGARCH_SUPPORT: Support LoongArch.CAPSTONE_M680X_SUPPORT: Support M680X.CAPSTONE_M68K_SUPPORT: Support M68K.CAPSTONE_MIPS_SUPPORT: Support Mips.CAPSTONE_MOS65XX_SUPPORT: Support MOS65XX.CAPSTONE_PPC_SUPPORT: Support PPC.CAPSTONE_SPARC_SUPPORT: Support Sparc.CAPSTONE_SYSTEMZ_SUPPORT: Support SystemZ.CAPSTONE_XCORE_SUPPORT: Support XCore.CAPSTONE_TRICORE_SUPPORT: Support TriCore.CAPSTONE_X86_SUPPORT: Support X86.CAPSTONE_TMS320C64X_SUPPORT: Support TMS320C64X.CAPSTONE_M680X_SUPPORT: Support M680X.CAPSTONE_EVM_SUPPORT: Support EVM.CAPSTONE_WASM_SUPPORT: Support Web Assembly.CAPSTONE_BPF_SUPPORT: Support BPF.CAPSTONE_RISCV_SUPPORT: Support RISCV.
Module registration
If you're building a static library that you intend to link into multiple consumers,
and they have differing architecture requirements, you may want -DCAPSTONE_USE_ARCH_REGISTRATION=1.
In your consumer code you can call cs_arch_register_*() to register the specific module for initialization.
In this way you only pay footprint size for the architectures you're actually using in each consumer, without having to compile Capstone multiple times.
Additional options
Capstone allows some more customization via the following options:
CAPSTONE_BUILD_SHARED_LIBS: Build shared libraries.CAPSTONE_BUILD_STATIC_LIBS: Build static libraries (ONby default).CAPSTONE_BUILD_STATIC_MSVC_RUNTIME: (Windows only) - Build with static MSVC runtime. Always set ifCAPSTONE_BUILD_SHARED_LIBS=ON.CAPSTONE_BUILD_CSTOOL: Enable/disable build ofcstool. Default is enabled if build runs from the repository root.CAPSTONE_USE_SYS_DYN_MEM: change this to OFF to use your own dynamic memory management.CAPSTONE_BUILD_MACOS_THIN: MacOS only. Disables universal2 build. So you only get the binary for you processor architecture.CAPSTONE_BUILD_DIET: change this to ON to make the binaries more compact.CAPSTONE_X86_REDUCE: change this to ON to make X86 binary smaller.CAPSTONE_X86_ATT_DISABLE: change this to ON to disable AT&T syntax on x86.
By default, Capstone use system dynamic memory management, and both DIET and X86_REDUCE
modes are disabled. To use your own memory allocations, turn ON both DIET &
X86_REDUCE, run "cmake" with: -DCAPSTONE_USE_SYS_DYN_MEM=0, -DCAPSTONE_BUILD_DIET=1, -DCAPSTONE_X86_REDUCE=1
Developer specific options
CAPSTONE_DEBUG: Change this to ON to enable extra debug assertions. Automatically enabled withDebugbuild.CAPSTONE_BUILD_CSTEST: Buildcstestinsuite/cstest/. Note:cstestrequireslibyamlon your system. It attempts to build it from source otherwise.CMAKE_EXPORT_COMPILE_COMMANDS: To exportcompile_commands.jsonforclangdand other language servers.ENABLE_ASAN: Compiles Capstone with the address sanitizer.ENABLE_COVERAGE: Generate coverage files.CAPSTONE_BUILD_LEGACY_TESTS: Build some legacy integration tests.
Building cstest
cstest is build together with Capstone by adding the flag -DCAPSTONE_BUILD_CSTEST.
The build requires libyaml. It is a fairly common package and should be provided by your package manager.
Note: Currently cstest us only supported on Linux.
If you run another operation system, please install cstest_py.
See bindings/python/BUILDING.md for instructions.