CMakeLists chain doesn't honour path variables.

[lr-morales]

At this moment, some CMakeLists.txt have hardcoded some of the installation paths, like /usr/local/ for base install path and /usr/lib/python2.7 for the location of Python. This would make users who need or want different destination paths for JdeRobot or with a non-standard python locations unable to change the paths for their installations in an easy way.

For the base install path, the CMake variable CMAKE_INSTALL_PREFIX should be used, as this is the variable that - under the view of CMake - marks the path prefix of main installation for a project.
In case of other path dependencies like the python one, we should use non-hardcoded methods when possible; i. e. worst case for python would be "asking the interpreter where the libraries should be"... meaning that the python interpreter location should be located too).

This would also mean that tools (like visualHFSM) or drivers of JdeRobot should not assume they or jderobot will reside in /usr/local in their code. This can be solved changing the sources to allow the usage of CMake functions like configure_file to resolve the installation path when running cmake.

[fqez]

I think this is a better solution for the installation of the project. Hardcoded paths could generate several headaches in the future. So I say yes to your proposal!