building on linux and confused by .so, .so.0, .so.0.9.4-dirty etc.

[sgehrman]

I have built this in the past on linux and just got .so files and that seemed very simple.

Now when I build I get all this weirdness:

libggml-base.so libggml.so.0.9.4-dirty
libggml-base.so.0 libggml-vulkan.so
libggml-base.so.0.9.4-dirty libggml-vulkan.so.0
libggml-cpu.so libggml-vulkan.so.0.9.4-dirty
libggml-cpu.so.0 libllama.so
libggml-cpu.so.0.9.4-dirty libllama.so.0
libggml.so libllama.so.0.0.1
libggml.so.0

Why did this change? Do I need to bundle all this with my app now?

Is there a compile flag to get just simple .so files as output?

[sgehrman]

and can I get rid of the symlinks? Why is this made so overly complex?

[lilydjwg]

They are there to allow multi-version installation of shared libraries in general. .so is for linking to a specific version and not used at runtime. .so.X is the soname which is used in runtime which changes when the ABI is imcompatible and thus programs should be re-linked. .so.X.whatever is the actual library version, which changes for every code change.

You can remove the .so (no suffix) symlinks if you don't intend to link other programs against them later.

Why did this change? Do I need to bundle all this with my app now?

Why not?