Because they are libraries. Why invent a whole new vendor-specific extension for what is exactly the same thing as their already-vendor-specific libraries?
More Related Contents:
- Why are LIB files beasts of such a duplicitous nature?
- Why does GCC create a shared object instead of an executable binary according to file?
- Convert a Static Library to a Shared Library?
- What is the use of .exp and what is the difference between .lib and .dll?
- Difference between static and shared libraries?
- When to use dynamic vs. static libraries
- building a .so that is also an executable
- Call Go functions from C
- Linking two shared libraries with some of the same symbols
- Merge multiple .so shared libraries
- Why am I getting a gcc “undefined reference” error trying to create shared objects?
- How to compile a static library in Linux?
- When / How does Linux load shared libraries into address space?
- gcc will not properly include math.h
- Build .so file from .c file using gcc command line
- What are .a and .so files?
- How to merge two windows vc static library into one
- Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
- How to link to a static library in C?
- How to create static linked shared libraries
- What exactly does `-rdynamic` do and when exactly is it needed?
- How can a shared library (.so) call a function that is implemented in its loader code?
- “relocation R_X86_64_32S against ” linking Error
- How to build a DLL from the command line in Windows using MSVC
- dyld: Library not loaded: ….. How to correctly tell GCC Compiler where to find another static library?
- Convert a Static Library to a Shared Library (create libsome.so from libsome.a): where’s my symbols?
- How do I build OpenSSL statically linked against Windows runtime?
- Statically link ncurses to program
- Executing a shared library on Unix
- C++ static variable in .lib does not initialize