New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow 'make uninstall' w/out building or installing #13871
Comments
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Pirmin Kalberer (Pirmin Kalberer)
|
Author Name: Médéric RIBREUX (Médéric RIBREUX) Hello, bug triage... this is still true for QGIS 2.13 master ! When you use the instructions indicated in the INSTALL file and try to @make uninstall@ just after @ccmake ..@, you've got the following:
So you can't make a build directory, configure CMake with ccmake and make uninstall without having made at least one @make install@. But it seems to be a "CMake problem":https://cmake.org/Wiki/RecipeAddUninstallTarget and not a QGIS one. Should we delete this bug or try to find a workaround ?
|
Author Name: Sandro Santilli (@strk) is there a target that builds install_manifest.txt, to make it a dependency of the "uninstall" target ? |
Author Name: Giovanni Manghi (@gioman)
|
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. |
Author Name: Sandro Santilli (@strk)
Original Redmine Issue: 3813
Redmine category:build/install
Current 'make uninstall' rule requires a full build and install in order to work. It'd be useful if you could uninstall w/out building or installing first, in case you cleaned your build tree after installing...
The text was updated successfully, but these errors were encountered: