search for: machotargetinfo

...f you are using lld as a library and you want to programmatically create a LinkerOptions, it is unclear which options need to be set for a particular flavor. It seems like the concrete subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. Here is how I see it currently works: 1) The flavor determines the driver class instantia...

...lld as a library and you want to programmatically create a LinkerOptions, it is unclear which options need to be set for a particular flavor. >> >> It seems like the concrete subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. > > Not allowing Drivers to touch anything except for core args has a very > importa...

...re using lld as a library and you want to programmatically create a LinkerOptions, it is unclear which options need to be set for a particular flavor. > > It seems like the concrete subclass of TargetInfo will ultimately hold the flavor specific options. So can DarwinDriver get a copy of the MachOTargetInfo object and set its ivars based on the command line options? Previously, I thought of LinkerOptions as the options needed by the core-linking phase (resolver), and the WriterOptions were flavor specific. Not allowing Drivers to touch anything except for core args has a very important side effect....