search for: _inputfiles

...perate vector needed ? b) lld also has to invoke variation of parseFile function so that it returns a FileArchive instead of a vector of files, how does lld need to invoke ? c) If it returns a vector of files as specified in the ReaderArchiveOptions, all of them need to be added to the _inputFiles object Thanks Shankar Easwaran Qualcomm Innovation Center. On 10/19/2012 6:17 PM, Nick Kledzik wrote: > On Oct 19, 2012, at 3:41 PM, Shankar Easwaran wrote: > >> Hi, >> >> I have started to work on support for Reading archive libraries in lld and thought of using the llvm...

On Oct 19, 2012, at 3:41 PM, Shankar Easwaran wrote: > Hi, > > I have started to work on support for Reading archive libraries in lld and thought of using the llvm/lib/ArchiveReader for this. > > The ArchiveReader doesnot fully support GNU archive libraries (thin archives), do you think we should continue using llvm/lib/ArchiveReader ? > > I was chatting with Michael and

...w does lld need to invoke ? There is only one parseFile() is always returns a vector of File* objects. In the non-force-load case it would return a vector of one FileArchive*. > c) If it returns a vector of files as specified in the ReaderArchiveOptions, all of them need to be added to the _inputFiles object That already happens in appendFiles(). -Nick > On 10/19/2012 6:17 PM, Nick Kledzik wrote: >> On Oct 19, 2012, at 3:41 PM, Shankar Easwaran wrote: >> >>> Hi, >>> >>> I have started to work on support for Reading archive libraries in lld and though...

Hi, I have started to work on support for Reading archive libraries in lld and thought of using the llvm/lib/ArchiveReader for this. The ArchiveReader doesnot fully support GNU archive libraries (thin archives), do you think we should continue using llvm/lib/ArchiveReader ? I was chatting with Michael and looks like there have been discussions and small sketches done on reading archive