search for: 7f0aews7

...on. To demonstrate, the following > patch > produces directives that work with Visual Studio 2010 using the > now-deprecated > dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: http://msdn.microsoft.com/en-us/library/7f0aews7.aspx only talks about the "exestr" comment type being deprecated. I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that means the dependent library feature is also deprecated. /* beginning of patch */ > > Index: /home/ygao/LLVM/...

...". Regarding the ordering information of the libraries, I think for MSVC the libraries are supposed to follow lexical order in the same source file. I am not sure if there is any restriction across different source files. Here is a link to the MSDN doc: http://msdn.microsoft.com/en-us/library/7f0aews7%28v=vs.80%29.aspx It is probably not too hard to add a directive section to ELF similar to COFF. At the 2012 LLVM Dev Meeting, there was a presentation on adding Modules to C, which presented a way to use ObjC-style .map files to specify libraries, which may be relevant to this auto-linking featu...

.... To demonstrate, the following patch >> produces directives that work with Visual Studio 2010 using the now-deprecated >> dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: > http://msdn.microsoft.com/en-us/library/7f0aews7.aspx > only talks about the "exestr" comment type being deprecated. > I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that means the dependent library feature is also deprecated. To clarify, at one point LLVM IR had a way to lis...

Hi all, We plan to add some auto-linking support for Mach-O, and need a scheme for encoding this information in the LLVM IR. We would like the same scheme to be able to support Microsoft's #pragma comment(lib,...) and #pragma comment(library, ...) features eventually. The current proposal is as follows: -- #1. Extend module-level metadata flags (llvm.module.flags) to support two new