[llvm-bugs] [Bug 24616] [win] lld-link shouldn't depend on env vars to find libraries optionally

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=24616

Reid Kleckner <rnk at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #4 from Reid Kleckner <rnk at google.com> ---
(In reply to comment #3)
> No it doesn't. But how can you find a correct search path if no path is
> given via the environment variable? What does clang-cl do?

INCLUDE doesn't depend on the target architecture, so we're just getting lucky.

Nico, personally I feel like if the user has LIB set then we have to trust it.
It's what link.exe does. We can do whatever we want when LIB isn't set, though.

Clang currently tries to guess which version of VS you want and which Windows
SDK you're using if INCLUDE isn't set. The code and the guesses are pretty bad,
but we could make it better and share it with LLD.

Users have already hit issues with the Windows 10 SDK paths being stale, for
example:
http://lists.llvm.org/pipermail/llvm-dev/2015-August/089011.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150831/1944e8a9/attachment.html>