search for: mtrent

...ing the library name. There are a few different approaches to implementing this, and I am not particularly tied to one. I think that selecting the one that is in the best interest of the project and the most maintainable long term would be best. On Fri, Oct 11, 2019 at 10:12 PM Michael Trent <mtrent at apple.com> wrote: > Hi there, > > This tool has been around for a long time. Originally it gave people a way > to move a dylib to a new location without rebuilding, and then as a way to > make an existing dylib embeddable (@rpath). I wonder if this tool is really > necessar...

Hey everyone! Recently there has been some progress on LLVM-based tools for manipulating MachO binaries: llvm-objcopy has been gaining a lot of important bits to support MachO (it's relatively close to the point where one can implement the strip-like functionality), llvm-lipo is functional and supports most of cctools' lipo options (https://llvm.org/docs/CommandGuide/llvm-lipo.html). There

> On May 23, 2019, at 2:05 AM, James Henderson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I discussed this with Seiya off the mailing list yesterday, and this was the suggestion we came up with, on the basis that GNU objcopy has support for the renaming for GDB support, but it might be confusing to people who are new to the system, so we provide a more expected output