Andrew Kelley 5a65caa2a3 ability to build stage1 using only a zig tarball ... The main idea here is that there are now 2 ways to get a stage1 zig binary: * The cmake path. Requirements: cmake, system C++ compiler, system LLVM, LLD, Clang libraries, compiled by the system C++ compiler. * The zig path. Requirements: a zig installation, system LLVM, LLD, Clang libraries, compiled by the zig installation. Note that the former can be used to now take the latter path. Removed config.h.in and config.zig.in. The build.zig script no longer is coupled to the cmake script. cmake no longer tries to determine the zig version. A build with cmake will yield a stage1 zig binary that reports 0.0.0+zig0. This is going to get reverted. `zig build` now accepts `-Dstage1` which will build the stage1 compiler, and put the stage2 backend behind a feature flag. build.zig is simplified to only support the use case of enabling LLVM support when the LLVM, LLD, and Clang libraries were built by zig. This part is probably sadly going to have to get reverted to make package maintainers happy. Zig build system addBuildOption supports a couple new types. The biggest reason to make this change is that the zig path is an attractive option for doing compiler development work on Windows. It allows people to work on the compiler without having MSVC installed, using only a .zip file that contains Zig + LLVM/LLD/Clang libraries.		2020-12-07 17:27:09 -07:00
..
include	update to latest clang C headers	2020-12-04 15:39:16 -07:00
libc	add more mingw-w64 .def files	2020-12-03 18:03:34 -07:00
libcxx	update install files for LLVM 11rc1	2020-08-04 17:52:26 -07:00
libcxxabi	update install files for LLVM 11rc1	2020-08-04 17:52:26 -07:00
libunwind	update libunwind to llvm 11rc2	2020-08-25 14:13:14 -07:00
std	ability to build stage1 using only a zig tarball	2020-12-07 17:27:09 -07:00