search for: linkerinvoc

...were flavor specific. Here is how I see it currently works: 1) The flavor determines the driver class instantiated. 2) The driver transforms flavor specific options into a "core" ArgList; 3) LinkerOptions constructor requires a core ArgList and sets ivars base on the ArgList. 4) The LinkerInvocation object is constructed from LinkerOptions object. 5) The LinkerInvocation object instantiates a Target object from the LinkerOptions which also creates a TargetInfo object and passes ownership to of the TargetInfo to the Target object. This last step seems convoluted. Couldn't the Target...

...t; Here is how I see it currently works: > > 1) The flavor determines the driver class instantiated. > 2) The driver transforms flavor specific options into a "core" ArgList; > 3) LinkerOptions constructor requires a core ArgList and sets ivars base on the ArgList. > 4) The LinkerInvocation object is constructed from LinkerOptions object. > 5) The LinkerInvocation object instantiates a Target object from the LinkerOptions which also creates a TargetInfo object and passes ownership to of the TargetInfo to the Target object. This last step seems convoluted. Couldn't the Ta...