iris
00cc9309cb
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
65 lines
2.8 KiB
Plaintext
65 lines
2.8 KiB
Plaintext
To install Capstone, you should run `pip install capstone`.
|
|
|
|
If you would like to build and install Capstone with just the source distribution,
|
|
just run `python -m pip install .`, considering you are in the folder with setup.py in it.
|
|
|
|
In order to use this source distribution, you will need an environment that can
|
|
compile C code. On Linux, this is usually easy, but on Windows, this involves
|
|
installing Visual Studio and using the "Developer Command Prompt" to perform the
|
|
installation. See BUILDING.md for more information.
|
|
|
|
By default, attempting to install the python bindings will trigger a build of
|
|
the capstone native core. If this is undesirable for whatever reason, for
|
|
instance, you already have a globally installed copy of libcapstone, you may
|
|
inhibit the build by setting the environment variable LIBCAPSTONE_PATH. The
|
|
exact value is not checked, just setting it will inhibit the build. During
|
|
execution, this variable may be set to the path of a directory containing a
|
|
specific version of libcapstone you would like to use.
|
|
|
|
If you don't want to build your own copy of Capstone, you can use a precompiled
|
|
binary distribution from PyPI. Saying `pip install capstone` should
|
|
automatically obtain an appropriate copy for your system. If it does not, please
|
|
open an issue at https://github.com/capstone-engine/capstone.
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
Capstone is a disassembly framework with the target of becoming the ultimate
|
|
disasm engine for binary analysis and reversing in the security community.
|
|
|
|
Created by Nguyen Anh Quynh, then developed and maintained by a small community,
|
|
Capstone offers some unparalleled features:
|
|
|
|
- Support multiple hardware architectures: ARM, AARCH64 (ARMv8), Mips, PPC, Sparc,
|
|
SystemZ, XCore and X86 (including X86_64).
|
|
|
|
- Having clean/simple/lightweight/intuitive architecture-neutral API.
|
|
|
|
- Provide details on disassembled instruction (called “decomposer” by others).
|
|
|
|
- Provide semantics of the disassembled instruction, such as list of implicit
|
|
registers read & written.
|
|
|
|
- Implemented in pure C language, with lightweight wrappers for C++, C#, Go,
|
|
Java, NodeJS, Ocaml, Python, Ruby & Vala ready (available in main code,
|
|
or provided externally by the community).
|
|
|
|
- Native support for all popular platforms: Windows, Mac OSX, iOS, Android,
|
|
Linux, *BSD, Solaris, etc.
|
|
|
|
- Thread-safe by design.
|
|
|
|
- Special support for embedding into firmware or OS kernel.
|
|
|
|
- High performance & suitable for malware analysis (capable of handling various
|
|
X86 malware tricks).
|
|
|
|
- Distributed under the open source BSD license.
|
|
|
|
Further information is available at http://www.capstone-engine.org
|
|
|
|
|
|
[License]
|
|
|
|
This project is released under the BSD license. If you redistribute the binary
|
|
or source code of Capstone, please attach file LICENSE.TXT with your products.
|