I've checked this in. It's far from finished, but having it in the main svn should make development easier.
It's not enabled by default, but the pieces are there to make it run for the same targets as the old sig finder.
If it's not enabled, the rebuild-stubs and batch-rebuild-stubs targets will just skip the thumb2 platforms.
To enable it, you need
* The
capstone library + headers
* Set OPT_CAPSTONE_TOOLS=1 in your buildconf or command line
* Set CAPSTONE_TOOLS_INC and CAPSTONE_TOOLS_LINK to specify any compile and linker options needed to use locate the capstone headers and library.
* Make sure there aren't any overrides in the platform makefile.inc disabling stubs generation
I've uploaded a windows mingw build of the library to
https://app.box.com/s/sshu7dv0mebvnee6gvpsex46y2m18w51(edit: updated Jan 11 2016)
This works with the chdkshell toolchain, just extract the files somewhere (e.g. c:/capstone) and set:
CAPSTONE_TOOLS_INC=-Ic:/capstone/include
CAPSTONE_TOOLS_LINK=-Lc:/capstone/lib -lcapstone
From my limited testing, makefile changes shouldn't interfere with chdkshell. The OPT_CAPSTONE_TOOLS option shows up as a checkbox. However, the INC/LINK variables need to be set manually to use it (I avoided naming them OPT_* because chdkshell turns those into checkboxes). If someone wants to include the above library package with chdkshell, this could be automated.
For linux, you should be able to just download the source and configure/make/make install. Some distros also include capstone packages, but the 3.0.4 changelog says "ARM * Fixed a memory corruption bug on IT instruction." so you might want to make sure it's the latest version if you use a distro package.
I have not tested any of this on linux or with 64 bit toolchains. I wouldn't be surprised if there are some 64-bit related issues in the code I've written.