John, Won't that simply remove the source directories. With that prefix Dennis has installed under /home/dennis/.local. If the build directory is under ~/Applications/gnucash-3.1 then he will lose the manifest by using rm -rf on the source directory.
If he can locate the original build directory then issuing make uninstall from a terminal open in that directory. I have adopted the practice of putting the build directory inside the source directory and retaining both (I once found that the make uninstall procedure seems to reference the source directories not simply the manifest file or the build directories but I have never checked this out fully) until after I have removed a build. It doesn't cause any problems and keeps everything you need for an uninstall together. Dennis Your build directory is unlikely to be gnucash-3.1, that is most likely the source directory. Where it is located is the directory from which you originally executed the cmake command since you used absolute addressing to the source. It may be inside gnucash-3.1 if you used the mkdir <build> and cd <build> commands from the terminal open atgnucash-3.1 before issuing the make command. Here <build> is a generic notation for a filename for a build file. It will have whatever name you gave it at the time. The attached screenshot gives you the directory structure and files in the build directory note the dist_manifest.txt and install_manifest.txt. These will be present in your build directory. Selection_009.png <http://gnucash.1415818.n4.nabble.com/file/t375329/Selection_009.png> David Cousens ----- David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
