Build should include install option

[tranqui]

@FTurci comment in #50 thread:

Other remark: "make" should be followed by "make install" and we should not have plenty of executables copied everywhere. "cmake" has also a prefix option. This was a source of confusion when we tried to identify the issue.

[merrygoat]

My bad on copying the executable around, I will fix the integration tests to not do this.

[merrygoat]

There are 3 stages to the make process. "cmake" should prepare the makefile, "make .." should actaully compile the file and then "make install" should do post compilation things. There are a couple of requests here:

• Provide option to "cmake" to set directory the binary is copied to by adding a parameter on compile
• Make more clear the default directory if a custom option is not used
• Add the lib directory to PYTHONPATH so the wrapper can be called directly
• Document all of this in the readme file

[merrygoat]

@tranqui Three out of the above 4 bullet points have been done in the latest build but I don't think I can edit PYTHONPATH from a cmake file in a platform independent way - correct me if I'm wrong.

[tranqui]

That’s fantastic Peter :)

Is it possible to move the library into the system python path then, so PYTHONPATH remains the same but it can still find the library?

[merrygoat]

No because python path is not just a directory, it is a series of directories that are searched - if you haven't used use python much it may well be that python path is not defined.

Can we just do it by adding current directory to sys.path in any Python scripts we provide? (as we have done in the unit tests). If users are writing their own scripts then they are probably sufficiently savvy to set PYTHONPATH. We can add a note to this effect in the readme too.

[tranqui]

Okay then, that seems like a reasonable compromise. I can write something in the readme for *NIX users if you like