Displaying 3 results from an estimated 3 matches for "msvctoolchain".
2015 Sep 03
4
LLVM 3.7.0 build errors on Windows
I'm working on a cross-platform project which links (statically) against
LLVM, which I use for MCJIT purposes.
Everything was fine on 3.4.2. I'm just experimenting with upgrading to
3.7.0, and everything works fine on OSX & Linux once I changed my
project to reflect the API updates.
On Windows, I get a bunch of compile errors - hundreds of them, but
variations on a couple of
2014 Oct 27
2
[LLVMdev] LLVM Weekly - #43, Oct 27th 2014
...g commits
* C compilation defaults to C11 by default, matching the behaviour of GCC 5.0.
[r220244](http://reviews.llvm.org/rL220244).
* Clang should now be better at finding Visual Studio in non-standard setups.
[r220226](http://reviews.llvm.org/rL220226).
* The Windows toolchain is now known as MSVCToolChain, to allow the addition a
CrossWindowsToolChain which will use clang/libc++/lld.
[r220362](http://reviews.llvm.org/rL220362),
[r220546](http://reviews.llvm.org/rL220546).
## Other project commits
* The libcxxabi gained support for running libc++abi tests with sanitizers.
[r220464](http://reviews....
2015 Jun 12
2
[LLVMdev] Self compiling latest clang from SVN
Makes sense, yeah, trying something in a different environment is usually a
good way to find problems. I had indeed moved the renamed clang-cl.exe to a
different directory, but when I move it back into its home directory and
retry the build, I get the same errors.
On Thu, Jun 11, 2015 at 11:16 PM, Reid Kleckner <rnk at google.com> wrote:
> Thanks for trying the self-host, it's