Capstone disassembly/disassembler framework: Core (Arm, Arm64, BPF, EVM, M68K, M680X, MOS65xx, Mips, PPC, RISCV, Sparc, SystemZ, TMS320C64x, Web Assembly, X86, X86_64, XCore) + bindings. (bloaty 依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Nguyen Anh Quynh b158b93a7d remove myinttypes.h 9 years ago
..
Capstone.xcodeproj remove myinttypes.h 9 years ago
CapstoneFramework Deleted unreferenced CapstoneFramework file 10 years ago
README.md Added README file; removed dubious config lines 10 years ago

README.md

Xcode Project for Capstone

The Capstone.xcodeproj project is an Xcode project that mimicks the Visual Studio solution for Capstone. It embeds nicely into Xcode workspaces. It has 13 targets, two of which are the most likely to be of interest:

  • CapstoneStatic, producing libcapstone.a, Capstone as a static library;
  • CapstoneDynamic, producing libcapstone.dylib, Capstone as a shared library;
  • test, test_arm, test_arm64, test_detail, test_mips, test_ppc, test_skipdata, test_sparc, test_systemz, test_xcore, testing all the things.

The project is configured to include all targets and use the system implementations of malloc, calloc, realloc, free and vsnprintf. This can be modified by editing the Preprocessor Macros build setting of either CapstoneStatic or CapstoneDynamic, whichever you plan to use. These settings are all at the target level: no specific overrides were used at the project level.

A Word of Warning: Static vs. Shared Library

There is a bug in how Xcode handles static libraries and dynamic libraries of the same name. Currently, if you integrate the Capstone project in a workspace and both the static and the dynamic libraries are built, if you try to link against either, you will always link against the dynamic one. To work around this issue, you can avoid building the dynamic library if you don't plan to use it, or you could change the Product Name build setting of either.