Find a file
Andrew Kelley dc478687d9 delete all stage1 c++ code not directly related to compiling stage2
Deleted 16,000+ lines of c++ code, including:
 * an implementation of blake hashing
 * the cache hash system
 * compiler.cpp
 * all the linking code, and everything having to do with building
   glibc, musl, and mingw-w64
 * much of the stage1 compiler internals got slimmed down since it
   now assumes it is always outputting an object file.

More stuff:
 * stage1 is now built with a different strategy: we have a tiny
   zig0.cpp which is a slimmed down version of what stage1 main.cpp used
   to be. Its only purpose is to build stage2 zig code into an object
   file, which is then linked by the host build system (cmake) into
   stage1. zig0.cpp uses the same C API that stage2 now has access to,
   so that stage2 zig code can call into stage1 c++ code.
   - stage1.h is
   - stage2.h is
   - stage1.zig is the main entry point for the Zig/C++
     hybrid compiler. It has the functions exported from Zig, called
     in C++, and bindings for the functions exported from C++, called
     from Zig.
 * removed the memory profiling instrumentation from stage1.
   Abandon ship!
 * Re-added the sections to the README about how to build stage2 and
   stage3.
 * stage2 now knows as a comptime boolean whether it is being compiled
   as part of stage1 or as stage2.
   - TODO use this flag to call into stage1 for compiling zig code.
 * introduce -fdll-export-fns and -fno-dll-export-fns and clarify
   its relationship to link_mode (static/dynamic)
 * implement depending on LLVM to detect native target cpu features when
   LLVM extensions are enabled and zig lacks CPU feature detection for
   that target architecture.
 * C importing is broken, will need some stage2 support to function
   again.
2020-09-17 18:29:38 -07:00
.builds Revert "disable sourcehut freebsd CI checks" 2020-09-14 19:43:26 -07:00
.github Sponsors Button => ZSF 2020-07-11 18:33:56 -04:00
ci ci: undo mangled autocrlf files before building 2020-09-16 11:58:26 -07:00
cmake Fixing dylib search path 2020-09-01 13:53:12 -04:00
deps deps/SoftFloat-3e/: commit with LF line endings 2020-05-31 12:18:31 -04:00
doc update the zen of zig 2020-09-15 13:40:01 -07:00
lib Merge remote-tracking branch 'origin/master' into stage2-zig-cc 2020-09-15 18:04:37 -07:00
src delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -07:00
src-self-hosted delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -07:00
test Merge remote-tracking branch 'origin/master' into stage2-zig-cc 2020-09-14 21:57:01 -07:00
tools fix tools/process_headers.zig regression 2020-08-30 21:24:41 -07: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
BRANCH_TODO delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -07:00
build.zig delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -07:00
CMakeLists.txt delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -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 delete all stage1 c++ code not directly related to compiling stage2 2020-09-17 18:29:38 -07:00

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 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 == 10.x, compiled with the same gcc or clang version above
Windows
  • cmake >= 3.15.3
  • Microsoft Visual Studio. Supported versions:
    • 2015 (version 14)
    • 2017 (version 15.8)
    • 2019 (version 16)
  • LLVM, Clang, LLD development libraries == 10.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

You will now run into this issue: homebrew and llvm 10 packages in apt.llvm.org are broken with undefined reference to getPollyPluginInfo or error: unable to create target: 'Unable to find target for this triple (no targets are registered)', in which case try -DZIG_WORKAROUND_4799=ON

Hopefully this will be fixed upstream with LLVM 10.0.1.

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 code. Even more important, however, are the end users.

Zig is intended to be used to help end users accomplish their goals. For example, it would be inappropriate and offensive to use Zig to implement dark patterns and it would be shameful to utilize Zig to exploit people instead of benefit them.

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 to users.

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.