Open MatthijsBurgh opened 6 months ago
Ah, it looks like this is something provided by ament_cmake
. Thanks! TDIL...
I think this is all defined in the
build_base/PKG_NAME/install_manifest.txt
.
As a personal anecdote, looking through a workspace with Nav2, most install_manifest.txt
files look empty? :thinking:
Aside from that, having to check a build base path in order to delete a package's install base path adds a conditional order of operations. E.g. if the build base path was cleaned prior and no longer exists, then we'd have no install_manifest
to rely on. Any suggestions on how to handle this? That, and the case where a package provides a install_manifest
, but never includes anything, or packages unrelated to cmake?
The locations a package can be installed can be determined by the package itself. I think this is all defined in the
build_base/PKG_NAME/install_manifest.txt
. I think deleting the files from file is the most robust solution.As the current implementation only deletes
install_base/PKG_NAME
. Though, this directory never exists.Any solution based on patterns will be incomplete.
Looking forward to your opinion.