search for: darwinopt

...rename the "ld64" flavor to "darwin". The command line tool on MacOSX is called "ld" - just like on unix. The name ld64 is the current source repository name for the linker. Once lld takes over, the term ld64 won't mean anything. I've worked through adding DarwinOpts.td new DarwinDriver class, but have some questions about wiring it up. Currently the instantiated Driver transforms the command line arguments in to "core" arguments which is passed to generatedOptions() to construct a LinkerOptions object. Is the plan for LinkerOptions to contain t...

On Jan 24, 2013, at 2:45 AM, Michael Spencer wrote: > On Wed, Jan 23, 2013 at 6:57 PM, Nick Kledzik <kledzik at apple.com> wrote: >> I've worked through adding DarwinOpts.td new DarwinDriver class, but have some questions about wiring it up. Currently the instantiated Driver transforms the command line arguments in to "core" arguments which is passed to generatedOptions() to construct a LinkerOptions object. >> >> Is the plan for LinkerOptio...

...st like on unix. The name ld64 is the current source repository name for the linker. Once lld takes over, the term ld64 won't mean anything. Sounds fine. We also need to figure how to determine when ld means binutils ld and when it means darwin ld. > > I've worked through adding DarwinOpts.td new DarwinDriver class, but have some questions about wiring it up. Currently the instantiated Driver transforms the command line arguments in to "core" arguments which is passed to generatedOptions() to construct a LinkerOptions object. > > Is the plan for LinkerOptions to con...