Try to switch default open source Windows build instructions to be clang |
||
Issue description(mostly just a placeholder for continuing discussion) It'd be nice if we could just require the SDK and then pull clang binaries like we do on Mac, etc. on Windows too, without ever installing VS. The Windows SDK has the headers, as well as rc.exe, mt.exe, midl.exe, etc. The main thing that would still be required from MSVC is link.exe, however lld for Windows is in progress and is somewhat usable now. I tried this in a VM and the first thing I hit was the clang update script trying to copy the DIA dll (which is MSVC, not SDK).
,
Jan 13 2017
I believe it links (?) but not so much with debugging/PDBs yet. So it might be a bit premature, but reasonable to see if we can get things working anyway. (My info might also be out of date.)
,
Jan 13 2017
lld works except it doesn't produce PDBs yet, so no debugging info. Other than that, we have a couple bots that build with lld in popular configs and everything builds and all tests pass. Re dia dlls: Looks like I added that in https://codereview.chromium.org/1879753002 IIRC llvm-symbolizer uses dia for symbolizing (once the PDB code in LLVM is complete, it won't necessarily be needed still), and llvm-symbolizer is used by the ASan runtime to print symbolized ASan stacks. So we could make that a warning instead of an error -- some things (ASan) will work a bit less well without the dll present, but most things will still work.
,
Jan 10
Archiving P3s older than 1 year with no owner or component. |
||
►
Sign in to add a comment |
||
Comment 1 by dpranke@chromium.org
, Jan 13 2017