[build2] Using build2 with clang 6 (trunk) on windows

[Boris Kolpackov]

Username I Wanted Was Already Taken <usernameiwantedwasalreadytaken at gmail.com> writes:

> Here it is (I skipped the first few lines of "trace: main..." because these
> e-mails are public... hope you don't mind):

Sure, thanks for the log. I believe I have figured it out and fixed.


> I don't know a way to query that, but will look into it.

Great, thanks. For the time being I've hardcoded it as 14.1.


> Actually no. I can run Clang (and build2) from a normal command line
> prompt. Of course I can also run from a Visual Studio Command Prompt, but
> that gives me the same result. Clang searches for the MSVC environment
> variables by itself, see:
> 
> https://github.com/llvm-mirror/clang/blob/master/lib/Driver/ToolChains/MSVC.cpp

Yes, I remember a long thread on cfe-dev where this was discussed. Sounded
hairy, to put it mildly. I think as a first step let's assume build2 is
run from the corresponding developer command prompt, just as we do with
VC currently.


> C:\Tests\Build2\hello\clang-6>clang -print-search-dirs
> programs: =C:\LLVM\build\bin
> libraries: =C:\LLVM\build\lib\clang\6.0.0

I was hoping for the MSVC/SDK toolchain paths in programs. But no luck.

Ok, I've staged a new version which fixes the target triplet issue and
also re-maps the target for Clang on Windows. Can you give it a try (from
the developer command prompt)? You should be able to upgrade it with bpkg
(i.e., bpkg fetch && bpkg build build2).

Boris