Rot127
Rot127
Hope I find time to review it next week. @santalvarez If you want to, feel free to leave your review here as well.
> I will try to see if I can reuse the cstest_py code. I think it should be fine as long as swift build succeeds. I am not familiar with...
@santalvarez Do you see cooporation potential btw? Since you folks work on the same problem.
> if this pr just adds a bunch of links, why not just keep the script and generate them for the release zip/tarball and keep the sources clean? Good point....
cc @hainest Because you did so many of the recent x86 improvements. @jxors Would you mind opening a draft PR with this patch? We can quickly check if any test...
This update would be great! I highly recommend to follow the [RefactorGuide](https://github.com/capstone-engine/capstone/blob/next/suite/auto-sync/RefactorGuide.md). Also, if you have trouble with something or want to have details or explanations, please let me know....
Yes, though let's wait until the Capstone PRs are merged.
For the website we could also do something like this (although it is pretty long. Not sure if it is worth it to use so much space for the list):
It looks for sure better. Though I don't know if people would click on it. Maybe using some `i` icon (for details/information)?
Made your changes. Test release so we can check it: https://github.com/Rot127/cutter/releases/tag/test-release-pkg-plugins