Re: Not in IT...
> surely you could just configure the linker to look in that location
Why yes you could, however that isn't the problem being solved by a library. A linker is a compile time process. It's the thing that grabs all the compiled objects and bundles them into an executable or library.
A library is something that allows you to load a library at runtime. As long as the interfaces are compatible, it means you can upgrade or replace one component without touching anything else. Symlinks allow you to install side by side versions of the same library without "DLL hell". (Different applications on a given system may require different versions of the same libraries to function. This often happens when you have a legacy application linked to an older version of a third party library together with a newer version which uses some bells and whistles not available in the old version.)