![]() |
![]() ![]()
Experimental Physics and
| ||||||||||||||
|
The idea was: In case the make install run installed (copied over) the configure directory under INSTALL_LOCATION, it should also remove it when doing "make uninstall". If INSTALL_LOCATION == TOP (the "normal" case), configure is already in place, not being created and should not be removed. I still think that "make uninstall" should remove everything that the build created under INSTALL_LOCATION. Maybe the if clause is not appropriate? Installing multiple modules into one location is indeed a dangerous mode of operation. Even without that rule, running "make uninstall" in *any* of the modules will remove the installed binaries, libraries, includes, dbd files of *all* modules, which doesn't seem right. The right thing would be saving the list of all installed files during the build and have "make uninstall" remove exactly the files that were installed. But that is actually what package managers are about, and pretty much out-of-scope for the build itself. Sorry for the inconvenience - not intended. ~Ralph On Fri, Jun 15, 2018 at 4:50 PM Andrew Johnson <[email protected]> wrote: On 06/15/2018 04:40 PM, Mark Rivers wrote:
| ||||||||||||||
ANJ, 20 Jun 2018 |
![]() · Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |