Add SONAME when Dynamically-Linked

[SoujiThenria]

Describe the feature

Add a SONAME to the dynamically linked version of Concord and increase it when breaking changes are made to the ABI. This will ensure that dynamically linked programs can use the correct version of the library.

Acceptance criteria

• The dynamically linked library is built with a proper SONAME.
• During the installation, create a symbolic link that points to the versioned library file (e.g., libdiscord.so -> libdiscord.so.1).
• Increment the SONAME version when there are breaking changes to the ABI.

Additional context

I maintain the FreeBSD port for Concord and have noticed that no SONAME is currently set when building the shared library. Since the SONAME is required by FreeBSD's port system, it makes sense to have it when distributing shared libraries to ensure that an application uses the right library version.

[HackerSmacker]

Whoa, I'm about 5 days late on this one -- yeah, this is pretty good. I can retouch the Makefile to include this.

[SoujiThenria]

On Fri Feb 28, 2025 at 11:25 PM CET, HackerSmacker wrote: HackerSmacker left a comment (Cogmasters/concord#192) Whoa, I'm about 5 days late on this one -- yeah, this is pretty good. I can retouch the Makefile to include this.

Thanks, that would be awesome! I gave it a shot myself but ran into some issues, getting the shared library link to be created only when it’s built while keeping the Makefile(s) cross-compatible.

[HackerSmacker]

I did submit a PR for this that addresses this and retains compatibility, I just haven't dragged the other folks into a review just yet.