Installation schemes for python

[sflis]

The problem now is that setup.py simply copies the extensions to the install location without changing the link path in library. Either we use patchelf while installing the python package (this assumes that the C++ libraries have already been installed and we can figure out the location of those) or installation of everything is handled by cmake (then it automatically sets the correct link path when copying the libraries).

Even if cmake is handling the install the python package setup should be handled by distutils and pip so that the package is correctly registered and we later can easily add consol-scripts as applications.

[sflis]

So this seems to be mostly fixed with a4eba84, however I let this issue stay as the final installation procedure has not yet been decided.

[sflis]

With the changes made in #11, the current python installation with setup.py makes two copies of the extensions in the _ext folder. One of the original file and one of the symlink (which has the correct module name). This should be fixed somehow by excluding files which have .so or .dylib extensions