You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[install] There is no uninstall target created by CMake #619
I'm upgrading from v1.3.1 to v1.4.0 in my Ubuntu 16.04 and I want to do a clean install. So I entered the v.1.3.1 folder that I had previously compiled and generated the Makefile and ran make uninstall but the rule uninstall doesn't exist. Is there an easy way to uninstall it that doesn't involve searching and deleting all files manually from my system?
@FreddieOliveira: What about make clean and delete the project folder afterwards? As far as I am aware of, currently no files are spread throughout the system in linux/unix environments apart from manual settings such as udev- or modprobe-rules. Please correct me if this is wrong.
What do others think about implementing an uninstall target?
What about make clean and delete the project folder afterwards?
Deleting the build directory would only purge the files inside it, leaving the ones added by the make install still hanging around on my system.
As far as I am aware of, currently no files are spread throughout the system
Version 1.3.1 was released February 2017 whereas version 1.4 was released in July that year. There's no way I would remember exactly which files were added to my system when make install was issued 5 months earlier. I didn't know by that time the Cmake creates a file called install_manifest.txt which lists all files added to your system, so in my mind the only solution was to run the make install again and check its output, or to use find.
Although the @xor-gate solution ( xargs rm < install_manifest.txt) works flawless, it'd still be nice to have an uninstall target.
No! I did implement that - look at the referenced commit (17 hours ago) just before I asked you to test. This targeted that commit of course. You seem to have tried with an older commit.
Now you have created a duplicate of that.
Yes, it will merge into the next release v1.6.1. You can track the related milestone. It's description should provide you with all info there is so far, including the release date (may be subject to change though, depending on progress). It is updated regularly so you should not worry to miss anything.
If you want to keep track with current changes and fixes, please stay on the develop branch.
Activity
xor-gate commentedon Jul 18, 2017
There is currently no uninstall target created with CMake. It has not been implemented but this is what they explain on the wiki: https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake
[-]Cannot find easy way to uninstall[/-][+]There is not uninstall target created by CMake[/+]FreddieOliveira commentedon Jul 18, 2017
Thank you
Nightwalker-87 commentedon Mar 25, 2020
@FreddieOliveira: What about
make cleanand delete the project folder afterwards? As far as I am aware of, currently no files are spread throughout the system in linux/unix environments apart from manual settings such as udev- or modprobe-rules. Please correct me if this is wrong.What do others think about implementing an uninstall target?
FreddieOliveira commentedon Mar 25, 2020
Deleting the build directory would only purge the files inside it, leaving the ones added by the
make installstill hanging around on my system.Version 1.3.1 was released February 2017 whereas version 1.4 was released in July that year. There's no way I would remember exactly which files were added to my system when
make installwas issued 5 months earlier. I didn't know by that time the Cmake creates a file calledinstall_manifest.txtwhich lists all files added to your system, so in my mind the only solution was to run themake installagain and check its output, or to usefind.Although the @xor-gate solution (
xargs rm < install_manifest.txt) works flawless, it'd still be nice to have an uninstall target.19 remaining items
FreddieOliveira commentedon Apr 6, 2020
But I don't get it, https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake suggests modifying
CMakeLists.txtand creating a new filemake_uninstall.cmake.in, but none of these changes were made.I took my time however to contribute helping you guys with this pull request: #907
Nightwalker-87 commentedon Apr 6, 2020
No! I did implement that - look at the referenced commit (17 hours ago) just before I asked you to test. This targeted that commit of course. You seem to have tried with an older commit.
Now you have created a duplicate of that.
FreddieOliveira commentedon Apr 6, 2020
Ooh, now I see. This was pushed into the
ext_pkg_versionsbranch, I was testing with the master. My bad.Indeed it fixes, thanks. Closing the issue as well as the duplicated PR. Just to know, when you intend to merge this into the master branch?
Nightwalker-87 commentedon Apr 6, 2020
Good, so it's not related to #804 then.
Yes, it will merge into the next release v1.6.1. You can track the related milestone. It's description should provide you with all info there is so far, including the release date (may be subject to change though, depending on progress). It is updated regularly so you should not worry to miss anything.
If you want to keep track with current changes and fixes, please stay on the
developbranch.Nightwalker-87 commentedon Apr 6, 2020
Fixed in commit e7ed76b.
Added cmake uninstall target