search for: addimplictfiles

Shankar, The LinkingContext has a addImplictFiles() method that is supposed to call the Writer and give it a chance to add any implicit files. Is the problem that the -u atoms are not attached to that implicit file? Or that the implicit file is not getting added? Or that this got lost in the transition from InputFiles to InputGraph? -Nick On...

Hi, Right now, linker added symbols specified by the -u option do not endup in the output YAML file. This is because the target specific Writers dont get called, which creates the undefined atoms. I am in the process of adding more options and I would like the atoms created internally by the options available in the output YAML file. The options that I am trying to consider for the linker

...vor also may want to add extra linker internal files in the future. I prefer addImplicitFiles calling the reader to add more files, which means addFiles API moves to the reader. Thanks Shankar Easwaran On 8/28/2013 4:57 PM, Nick Kledzik wrote: > Shankar, > > The LinkingContext has a addImplictFiles() method that is supposed to call the Writer and give it a chance to add any implicit files. Is the problem that the -u atoms are not attached to that implicit file? Or that the implicit file is not getting added? Or that this got lost in the transition from InputFiles to InputGraph? > > -...

...). Also for the case of -u, the Driver can make generic UndefinedAtoms. Other options may need platform specific atoms which may be created with the help of static Writer methods. -Nick > On 8/28/2013 4:57 PM, Nick Kledzik wrote: >> Shankar, >> >> The LinkingContext has a addImplictFiles() method that is supposed to call the Writer and give it a chance to add any implicit files. Is the problem that the -u atoms are not attached to that implicit file? Or that the implicit file is not getting added? Or that this got lost in the transition from InputFiles to InputGraph? >> &...