This is a page just for tinkerers. 

If you are not interested in code or perhaps writing your own game, this is not the page for you!

On the other hand, there are some deep explorations possible here, for those who can make the added link. 

Shared versus Static LibrariesEdit

If you plan to write your own game, you will need to learn about shared and static libraries. Most shared libraries are fairly large files ending with the .so extension for shared object. This file is a binary file, so you will not be able to skim it, the way you would a textbook. On the other hand, static libraries have the extension .a or in Windows .lib

Shared objects are great since you can simply replace the lbrary with a functionally equivalent library at some time in the future, without the dependent program needing to be recompiled!

A common metaphor is to say that a static library is like a bookstore while a shared library is like a - - library!

With the former, you get your own copy of the book/function to take home; with the latter you and everyone else go to the library to use the same book/function. So anyone who wants to use the (shared) library needs to know where it is, because you have to "go get" the book/function. With a static library, the book/function is yours to own, and you keep it within your home/program, and once you have it you don't care where or when you got it.  

The shared library is not compiled as part of the application, but can be loaded into an application at run-time, which is the general mechanism for implementing binary plug-in systems.

There is a good introduction to libraries here

> > More soon