make uninstall
In my opinion, make uninstall should:
- remove all header files in
/usr/local/include/ini-algorithms/wolf/
- remove folder
/usr/local/include/ini-algorithms/wolf/
- remove library
/usr/local/lib/iri-algorithms/libwolf.so
- remove folder
/usr/local/lib/cmake/wolf/
This should also apply to all plugins.
Currently, a number of bugs are hidden because dangling installed files live in the installation paths even when the library has changed. The only way to bullet-proof the system now is by making sure the whole wolf+plugins can compile and install from a completely clean system.
This uninstall feature leaves the machine clean from any dangling file.
The previous uninstall just removed the files that appeared in a list. If the list is changed (and it is, depending on the branch we use), then some files are not uninstalled.
Examples:
- file
pinhole_tools.h
was in core, and now is in vision. - plugins trying to find it in core will fail, or not, depending on the installation of core and the previous uninstalls. If no uninstalls have been performed, then it compiles because the file is still in the installation path!
- currently, vision/devel does not compile if one makes sure to completely uninstall and reinstall core/devel. Just reinstalling core/devel without a complete uninstall would leave
pinhole_tools.h
in the core installation place, and the bug would not be found.
Edited by Joan Solà Ortega