aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/ArchiveWriter.cpp
diff options
context:
space:
mode:
authorJason Molenda <jason@molenda.com>2022-09-09 17:34:23 -0700
committerJason Molenda <jason@molenda.com>2022-09-09 17:37:46 -0700
commit30578c08568bc8de79dea72e41f49899ba10ea55 (patch)
tree319f153bf5e225d5a1a669d19d0a6553460a0e60 /llvm/lib/Object/ArchiveWriter.cpp
parent467bb47c841897450990f3ab82e79fec5f2d1f60 (diff)
downloadllvm-30578c08568bc8de79dea72e41f49899ba10ea55.zip
llvm-30578c08568bc8de79dea72e41f49899ba10ea55.tar.gz
llvm-30578c08568bc8de79dea72e41f49899ba10ea55.tar.bz2
dependency cycle fix in DynamicLoaderDarwinKernel
DynamicLoaderDarwinKernel calls in to PlatformDarwinKernel, and with my changes in https://reviews.llvm.org/D133534, PlatformDarwinKernel calls in to DynamicLoaderDarwinKernel. This results in a cmake dependency if accurately included in the link libraries list. lldbPluginDynamicLoaderDarwinKernel is specfically for kernel debugging and is uncommonly linked in to anything except a full lldb. lldbPluginPlatformMacOSX is any Darwin platform, including PlatformDarwinKernel, and is referenced a number of time in shell tests, for instance. I believe anything linking the darwin kernel DynamicLoader plugin will already have lldbPluginPlatformMacOSX in its dependency list, so not explicitly expressing this dependency is safe.
Diffstat (limited to 'llvm/lib/Object/ArchiveWriter.cpp')
0 files changed, 0 insertions, 0 deletions