Taking a speculative guess - "so" just might stand for "shared object" ?
I still don't understand how they work. :|
Suppose we have a library (lib_something), and there might even be a (lib_something-dev), that one can install.
After install, there then also appears a (
lib_something.a) and often a (
lib_something.so) which take up their place in
/usr/lib, or sometimes
/usr/local/lib
These are in addition to ones like lib_something.h that appear in /usr/include/
In general terms, what are these "
.a" and "
.so" files, how do they get made, and what uses them? Thanks
