How do source releases map to binary releases?

[paul35621]

I often switch between different versions of Qt (both Qt 5 and Qt 6) and QtJambi. I download them from two sources:

• Source releases from GitHub: https://github.com/OmixVisualization/qtjambi/releases
• Binary releases from Maven: https://repo1.maven.org/maven2/io/qtjambi/qtjambi/

(are "source releases" and "binary releases" the right terms?)

I need the source releases because I wrote a Qt class in C++ and need to build Java bindings for it.

The difference in version numbers between the source releases and the binary releases keeps confusing me and I would like to have this cleared up.

If I have some binary release, let's say 5.15.18, how can I find the corresponding source version? Is there a pattern or can I call a function in the jar of a binary release to get it? Or should I inspect the source release to see what binary release it produces?

Update
Based on the answer, this is the mapping starting with source release 6.2:

6.7.0 → 5.15.20, 6.5.6, 6.6.3, 6.7.0
6.6.2 → 5.15.19, 6.5.5, 6.6.2
6.6.1 → 5.15.18, 6.5.4, 6.6.1
6.6.0 → 5.15.17, 6.5.3, 6.6.0
6.5.3 → 5.15.17, 6.5.3
6.5.2 → 5.15.16, 6.5.2
6.5.1 → 5.15.14, 6.5.1
6.5.0 → 5.15.14, 6.5.0
6.4.4 → 5.15.14, 6.2.12, 6.4.4
6.4.3 → 5.15.13, 6.2.11, 6.4.3
6.4.2 → 5.15.12, 6.2.10, 6.4.2
6.4.1 → 5.15.11, 6.2.9, 6.4.1
6.4.0 → 5.15.10, 6.2.8, 6.3.5, 6.4.0
6.3.4a → 5.15.9, 6.2.7, 6.3.4
6.3.4 → 5.15.9, 6.2.7, 6.3.4
6.3.3 → 5.15.8, 6.2.6, 6.3.3
6.3.2 → 5.15.7, 6.2.5, 6.3.2
6.3.1 → 5.15.6, 6.2.4, 6.3.1
6.3.0 → 5.15.5, 6.2.3, 6.3.0
6.2.2 → 5.15.4, 6.2.2
6.2.1 → 5.15.3, 6.2.1
6.2 → 5.15, 6.2

The first two numbers of the binary release (5.15, 6.2, etc.) are always equal to the first two numbers of the Qt version.

Just one more question to make this all clear: Which source release is used for binary releases 5.15.14, 5.15.17, 6.5.3 and 5.15.9/6.2.7/6.3.4? Or do the different source releases produce the same files?

[omix]

You can download the qtjambi-native for the platform you require. Unpack the content. You'll find include directory with all required headers. Download qtjambi-generator for generating bindings for your custom code. In qtjambi-generator-native you'll find the symbol file for Qtjambi DLL. Unpack it. Now you can compile your generated bindings.

Yes, the versioning of Qtjambi is quite confusing when you look at it independently. I try to keep the releases in sync with Qt's release cycle. For every new Jambi additional binaries are shipped for all current and LTS Qt versions. You can find all related binary versions in the modules page of each QtJambi release.

6.7.0 modules
6.6.1 modules

[paul35621]

Thanks for the quick answer! See my update for one more question. Nice to hear that I don't need to build QtJambi for compiling the bindings to my own Qt class, that will be a nice improvement to my build process.