When using llvm-libtool-darwin as a drop in replacement for cctools
libtool, Xcode expects you to create a dependency info file. This file
is a very simple format describing the input files, the output files,
and the version of the tool. This logic is mirrored from that of
ld64.lld, which supports creating this file as well. Ideally we could
extract it, but I don't think we want to throw this into one of the
grab-bag libraries given how small the logic is.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
LG (with a nit)
(I don't know who else needs to stamp this)
llvm/tools/llvm-libtool-darwin/llvm-libtool-darwin.cpp | ||
---|---|---|
665 | [nit] How important is performance for this tool, do you know? Is it worth removing the if (Active) check in the DependencyInfo class, and instead movign the logic here so that the check is done only once: GlobalDependencyInfo = DependencyInfoPath.empty() ? std::make_unique<DummyDependencyInfo>() // A subclass that doesn't do anything : std::make_unique<DependencyInfo>(DependencyInfoPath); |
Is this intentional? (ie., logging to errs()? ) I wonder if there's a "debug()" or something similar so that it'd look less suspicious)