Go to file
Vexu 98d5bfbd4d
update grammar in langref
2020-11-22 21:30:09 +02:00
.builds ci: use hut.lavatech.top for updating the download page 2020-09-14 19:37:59 -07:00
.github Sponsors Button => ZSF 2020-07-11 18:33:56 -04:00
ci Azure Pipelines CI: update msys2 to the current version 2020-11-15 00:27:18 +01:00
cmake fix cmake logic for checking LLVM version 2020-11-02 12:16:10 -07:00
deps Revert "Include dbg.h to third-party libs" 2020-10-03 21:29:29 -04:00
doc update grammar in langref 2020-11-22 21:30:09 +02:00
lib update grammar in langref 2020-11-22 21:30:09 +02:00
src Merge pull request #7182 from LemonBoy/externnnn 2020-11-21 09:41:49 -08:00
test Merge pull request #7165 from LemonBoy/ppc64final 2020-11-20 17:40:17 -08:00
tools stage2: Make zig cc more verbose (#7166) 2020-11-19 23:30:16 +01:00
.gitattributes .gitattributes: deps/SoftFloat-3e/*.txt lines are crlf terminated 2020-04-05 11:03:31 -04:00
.gitignore fix .gitignore file and add commit missing std lib file 2019-02-26 18:33:27 -05:00
CMakeLists.txt std: add std.atomic.Bool 2020-11-19 00:58:13 +11:00
CODE_OF_CONDUCT.md add a code of conduct 2020-10-08 22:48:16 -07:00
CONTRIBUTING.md add behavior tests fro macro translations 2020-07-16 17:10:52 +03:00
LICENSE add license 2015-08-05 16:22:18 -07:00
README.md Copy editing :) 2020-10-26 18:39:34 +01:00
build.zig Bump Zig version to 0.7.0 2020-11-08 23:50:44 +01:00

README.md

ZIG

A general-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

Resources

Building from Source

Build Status

Note that you can download a binary of the master branch or install Zig from a package manager.

Stage 1: Build Zig from C++ Source Code

This step must be repeated when you make changes to any of the C++ source code.

Dependencies

POSIX
  • cmake >= 2.8.5
  • gcc >= 5.0.0 or clang >= 3.6.0
  • LLVM, Clang, LLD development libraries == 11.x, compiled with the same gcc or clang version above
Windows
  • cmake >= 3.15.3
  • Microsoft Visual Studio. Supported versions:
    • 2017 (version 15.8)
    • 2019 (version 16)
  • LLVM, Clang, LLD development libraries == 11.x

Instructions

POSIX
mkdir build
cd build
cmake ..
make install

Need help? Troubleshooting Build Issues

MacOS
brew install cmake llvm
brew outdated llvm || brew upgrade llvm
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

Now we use the stage1 binary:

zig build --prefix $(pwd)/stage2 -Denable-llvm

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

This produces zig-cache/bin/zig.

Release / Install Build

stage2/bin/zig build install -Drelease

License

The ultimate goal of the Zig project is to serve users. As a first-order effect, this means users of the compiler, helping programmers to write better software. Even more important, however, are the end-users.

Zig is intended to be used to help end-users accomplish their goals. Zig should be used to empower end-users, never to exploit them financially, or to limit their freedom to interact with hardware or software in any way.

However, such problems are best solved with social norms, not with software licenses. Any attempt to complicate the software license of Zig would risk compromising the value Zig provides.

Therefore, Zig is available under the MIT (Expat) License, and comes with a humble request: use it to make software better serve the needs of end-users.

This project redistributes code from other projects, some of which have other licenses besides MIT. Such licenses are generally similar to the MIT license for practical purposes. See the subdirectories and files inside lib/ for more details.