26 Oct
2018
26 Oct
'18
2:34 p.m.
Edward Diener wrote:
I have rued the day I pushed clang-win.jam from someone elses posting because I wanted to test clang under Windows and it seemed to work. Mainly because I am not knowledgeable enough with bjam to "fix" clang-win.jam and no one else was ever interested in doing so.
It would have been nice if clang-cl.exe had an option to invoke the msvc tools it obviously knows how to find, so that we could call f.ex. "clang-cl.exe /lib <options>" and have it do the right thing for us. Unfortunately, it doesn't. It does have /link which can call link.exe for us, but this only works for shared libraries. Perhaps we can capture the output of clang-cl.exe -### foo.obj /link and extract the path to link.exe from there...