diff options
author | Petr Hosek <phosek@google.com> | 2019-12-27 16:25:43 -0800 |
---|---|---|
committer | Petr Hosek <phosek@google.com> | 2020-01-06 14:51:32 -0800 |
commit | 71a2a62163cfafbc31cd827106506c73ff49e8b5 (patch) | |
tree | 4493024f27631f161403e5c9ee6c65d2a17a8ea6 /lldb/packages/Python/lldbsuite/test | |
parent | 83d690a149802d40c711d4fb5a058dd1ebe4aa23 (diff) | |
download | bcm5719-llvm-71a2a62163cfafbc31cd827106506c73ff49e8b5.tar.gz bcm5719-llvm-71a2a62163cfafbc31cd827106506c73ff49e8b5.zip |
[CMake] Pass symlink dependency to add_llvm_install_targets explicitly
The install-${name}-stripped targets don't strip when ${name} is being
symlinked, e.g. llvm-ar or llvm-objcopy. The problem is that
llvm_install_symlink passes install-${dest} as a dependency of
install-${name}, e.g. install-llvm-ar becomes a dependency of both
install-llvm-ranlib and install-llvm-ranlib-stripped. What this means is
that when installing a distribution that contains both llvm-ar and
llvm-ranlib is that first the stripped version of llvm-ar is installed
(by the install-llvm-ar-stripped target) and then it's overwritten by an
unstripped version of llvm-ar bnecause install-llvm-ranlib-stripped has
install-llvm-ranlib as a dependency as mentioned earlier. To avoid this
issue, rather than passing the install-${dest} as dependency, we
introduce a new argument to add_llvm_install_targets for symlink target
which expands it into an appropriate dependency, i.e. install-${dest}
for install-${name} target and install-${dest}-stripped for
install-${name}-stripped.
Differential Revision: https://reviews.llvm.org/D71951
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions