capstone Java Bindings: New Constants Not In Jar

@Rot127 Not making a full issue because it's so small and I'm sure you probably caught it yourself, but I figured someone should let you know in case you didn't:

The change you made in https://github.com/capstone-engine/capstone/commit/cd282ef59324e28f1d59bbe12a0b2af535cc617f references a lot of variables that don't exist, and the ones that do aren't imported with import static capstone.Capstone.*.

I only noticed because I happened to try to copy the files directly from the repo like immediately after you committed it, lol

Mar 03 '25 05:03 ByThePowerOfScience

Yes, I've seen it. But ignored it tbh for now. Because there was https://github.com/capstone-engine/capstone/discussions/2291 going on. The Java bindings were abandoned for a while now. Even before the Auto-Sync effort started.

But are you using them successfully?

Mar 03 '25 13:03 Rot127

The Java bindings were abandoned for a while now. Even before the Auto-Sync effort started.

That's a big shame, I was about to start a massive project with them. Capstone was seeming like the perfect choice, too.

I'll download from a different commit then or see if I can't fudge the bindings myself using Panama.

Mar 04 '25 00:03 ByThePowerOfScience

If you need only one or two architectures, it shouldn't be too much effort to update them. Otherwise it is a little more effort I think.

But @peace-maker has a WIP update in their branch: https://github.com/peace-maker/capstone/tree/java_bindings (also see the comment: https://github.com/capstone-engine/capstone/discussions/2291#discussioncomment-12274567)

Maybe you can coordinate?

Mar 04 '25 17:03 Rot127