Go to file
Andrew Kelley 9e4065fa73
remove TODO regarding lazy values
The question was:

> // TODO do we need lazy values on vector comparisons?

Nope, in fact the existing code already was returning ErrorNotLazy
for that particular type, and would already goto
never_mind_just_calculate_it_normally. So the explicit check for
ZigTypeIdVector is not needed. I appreciate the caution though.
2019-09-18 10:54:45 -04:00
.builds freebsd ci: install wget and set -x -e 2019-03-18 23:44:29 -04:00
.github funding: I've been accepted into the GitHub Sponsors program 2019-07-11 13:00:39 -04:00
ci Get more of the tests passing for FreeBSD (#3197) 2019-09-10 14:50:54 -04:00
cmake cmake: allow user to select static vs dynamic LLVM 2019-07-16 12:33:13 -04:00
deps add patch to LLD to fix deadlock race condition in wasm linker 2019-04-16 03:56:46 -04:00
doc implement noasync function calls 2019-09-05 21:55:32 -04:00
lib update glibc src files to 2.30 2019-09-10 16:40:54 -04:00
src remove TODO regarding lazy values 2019-09-18 10:54:45 -04:00
src-self-hosted changing occurrences of HashMap with []const u8 as keys for StringHashMap 2019-09-03 23:53:05 +02:00
std update clone on arm32 to latest musl implementation 2019-09-16 14:23:43 -04:00
test stage1: proper return type on vector comparisons 2019-09-18 10:36:10 -04:00
tools update glibc ABI lists to 2.30 2019-09-07 15:04:09 -04:00
.gitattributes fix gitattributes 2019-07-16 00:05:12 -04:00
.gitignore fix .gitignore file and add commit missing std lib file 2019-02-26 18:33:27 -05:00
build.zig release builds of stage1 have llvm ir verification 2019-09-09 09:33:33 -04:00
CMakeLists.txt make the std lib support event-based I/O 2019-09-10 10:26:52 -04:00
CONTRIBUTING.md update CONTRIBUTING.md 2019-08-04 15:15:25 -04:00
LICENSE add license 2015-08-05 16:22:18 -07:00
README.md Use LLVM path provided by homebrew 2019-08-29 10:19:35 -04:00

ZIG

A general-purpose programming language designed for robustness, optimality, and maintainability.

Resources

Building from Source

Build Status

Note that you can download a binary of master branch.

Stage 1: Build Zig from C++ Source Code

Dependencies

POSIX
  • cmake >= 2.8.5
  • gcc >= 5.0.0 or clang >= 3.6.0
  • LLVM, Clang, LLD development libraries == 8.x, compiled with the same gcc or clang version above
Windows
  • cmake >= 2.8.5
  • Microsoft Visual Studio 2017 (version 15.8)
  • LLVM, Clang, LLD development libraries == 8.x, compiled with the same MSVC version above

Instructions

POSIX
mkdir build
cd build
cmake ..
make install
MacOS
brew install cmake llvm@8
brew outdated llvm@8 || brew upgrade llvm@8
mkdir build
cd build
cmake .. -DCMAKE_PREFIX_PATH=$(brew --prefix llvm)
make install
Windows

See https://github.com/ziglang/zig/wiki/Building-Zig-on-Windows

Stage 2: Build Self-Hosted Zig from Zig Source Code

Note: Stage 2 compiler is not complete. Beta users of Zig should use the Stage 1 compiler for now.

Dependencies are the same as Stage 1, except now you can use stage 1 to compile Zig code.

bin/zig build --prefix $(pwd)/stage2

This produces ./stage2/bin/zig which can be used for testing and development. Once it is feature complete, it will be used to build stage 3 - the final compiler binary.

Stage 3: Rebuild Self-Hosted Zig Using the Self-Hosted Compiler

Note: Stage 2 compiler is not yet able to build Stage 3. Building Stage 3 is not yet supported.

Once the self-hosted compiler can build itself, this will be the actual compiler binary that we will install to the system. Until then, users should use stage 1.

Debug / Development Build

./stage2/bin/zig build --prefix $(pwd)/stage3

Release / Install Build

./stage2/bin/zig build install -Drelease