Local build not set up

[omeh-a]

Currently the only way to sanely build ipbench is to package it as a deb and install that. This is awful for maintaining it. This is marked as a bug but in reality this was just never set up.

To do:
> Set up make install to do the right thing.

make already compiles correctly and puts output for ipbench itself in /src/lib/.libs and output for modules in /src/pymod/.libs + /src/tests/(test).

To actually install ipbench:

1. Put libipbench.so in /usr/local/lib (or /usr/lib) - hereby referred to as "lib"
2. Create folder lib/ipbench and put compiled ipbench modules here.
3. Install ipbench client/target .py in python/site-packages (or dist-packages) + libipbenchClientPython + libipbenchTargetPython + _ipbench_client.so + _ipbench_target.so.

Note: also include .la files with .so files. Apparently it is neccessary in some cases.

Python note: site local for pip or other local installs, dist packages for system wide

[omeh-a]

Minor tweaks to build system mostly fixed this in #7 - there is still an issue however in that automake's choice of where to put Python dependencies might be wrong.

[omeh-a]

Additional thing to do: might be nice to have all build output go into a local folder for testing so you don't need to repeatedly make install when testing.

[omeh-a]

Building locally now works fine, although it still likes to put python dependencies in the wrong place for modern distributions. This is minor however.

Bigger issue: the output format of building locally is not runnable. You have to make install for the code to sanely be executable. This isn't an issue for users, but it's obscenely annoying for testing new features.