2022-01-04 00:45:09 +00:00
|
|
|
|
2015-08-06 01:44:05 +01:00
|
|
|
|
2019-12-30 23:16:40 +00:00
|
|
|
A general-purpose programming language and toolchain for maintaining
|
|
|
|
|
**robust**, **optimal**, and **reusable** software.
|
2015-08-06 01:44:05 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
https://ziglang.org/
|
2016-02-10 05:31:49 +00:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
## Documentation
|
|
|
|
|
|
|
|
|
|
If you are looking at this README file in a source tree, please refer to the
|
|
|
|
|
**Release Notes**, **Language Reference**, or **Standard Library
|
|
|
|
|
Documentation** corresponding to the version of Zig that you are using by
|
|
|
|
|
following the appropriate link on the
|
|
|
|
|
[download page](https://ziglang.org/download).
|
|
|
|
|
|
|
|
|
|
Otherwise, you're looking at a release of Zig, and you can find documentation
|
|
|
|
|
here:
|
|
|
|
|
|
|
|
|
|
* doc/langref.html
|
|
|
|
|
* doc/std/index.html
|
2016-11-24 07:44:03 +00:00
|
|
|
|
2020-12-08 00:50:14 +00:00
|
|
|
## Installation
|
2015-12-07 04:55:28 +00:00
|
|
|
|
2020-12-08 00:50:14 +00:00
|
|
|
* [download a pre-built binary](https://ziglang.org/download/)
|
|
|
|
|
* [install from a package manager](https://github.com/ziglang/zig/wiki/Install-Zig-from-a-Package-Manager)
|
|
|
|
|
* [bootstrap zig for any target](https://github.com/ziglang/zig-bootstrap)
|
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-18 02:29:38 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
A Zig installation is composed of two things:
|
|
|
|
|
|
|
|
|
|
1. The Zig executable
|
|
|
|
|
2. The lib/ directory
|
|
|
|
|
|
|
|
|
|
At runtime, the executable searches up the file system for the lib/ directory,
|
|
|
|
|
relative to itself:
|
|
|
|
|
|
|
|
|
|
* lib/
|
2023-08-12 06:15:15 +01:00
|
|
|
* lib/zig/
|
2023-07-23 23:48:54 +01:00
|
|
|
* ../lib/
|
2023-08-12 06:15:15 +01:00
|
|
|
* ../lib/zig/
|
2023-07-23 23:48:54 +01:00
|
|
|
* (and so on)
|
|
|
|
|
|
|
|
|
|
In other words, you can **unpack a release of Zig anywhere**, and then begin
|
|
|
|
|
using it immediately. There is no need to install it globally, although this
|
|
|
|
|
mechanism supports that use case too (i.e. `/usr/bin/zig` and `/usr/lib/zig/`).
|
|
|
|
|
|
|
|
|
|
## Building from Source
|
|
|
|
|
|
|
|
|
|
Ensure you have the required dependencies:
|
|
|
|
|
|
2023-09-15 22:43:40 +01:00
|
|
|
* CMake >= 3.5
|
2023-07-23 23:48:54 +01:00
|
|
|
* System C/C++ Toolchain
|
2023-09-24 11:54:52 +01:00
|
|
|
* LLVM, Clang, LLD development libraries == 17.x
|
2023-07-23 23:48:54 +01:00
|
|
|
|
|
|
|
|
Then it is the standard CMake build process:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
mkdir build
|
|
|
|
|
cd build
|
|
|
|
|
cmake ..
|
|
|
|
|
make install
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
For more options, tips, and troubleshooting, please see the
|
|
|
|
|
[Building Zig From Source](https://github.com/ziglang/zig/wiki/Building-Zig-From-Source)
|
|
|
|
|
page on the wiki.
|
|
|
|
|
|
|
|
|
|
## Contributing
|
|
|
|
|
|
|
|
|
|
Zig is Free and Open Source Software. We welcome bug reports and patches from
|
|
|
|
|
everyone. However, keep in mind that Zig governance is BDFN (Benevolent
|
|
|
|
|
Dictator For Now) which means that Andrew Kelley has final say on the design
|
|
|
|
|
and implementation of everything.
|
|
|
|
|
|
|
|
|
|
One of the best ways you can contribute to Zig is to start using it for an
|
|
|
|
|
open-source personal project.
|
|
|
|
|
|
|
|
|
|
This leads to discovering bugs and helps flesh out use cases, which lead to
|
|
|
|
|
further design iterations of Zig. Importantly, each issue found this way comes
|
|
|
|
|
with real world motivations, making it straightforward to explain the reasoning
|
|
|
|
|
behind proposals and feature requests.
|
|
|
|
|
|
|
|
|
|
You will be taken much more seriously on the issue tracker if you have a
|
|
|
|
|
personal project that uses Zig.
|
|
|
|
|
|
|
|
|
|
The issue label
|
|
|
|
|
[Contributor Friendly](https://github.com/ziglang/zig/issues?q=is%3Aissue+is%3Aopen+label%3A%22contributor+friendly%22)
|
|
|
|
|
exists to help you find issues that are **limited in scope and/or knowledge of
|
|
|
|
|
Zig internals.**
|
2020-09-11 19:30:21 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
Please note that issues labeled
|
|
|
|
|
[Proposal](https://github.com/ziglang/zig/issues?q=is%3Aissue+is%3Aopen+label%3Aproposal)
|
|
|
|
|
but do not also have the
|
|
|
|
|
[Accepted](https://github.com/ziglang/zig/issues?q=is%3Aissue+is%3Aopen+label%3Aaccepted)
|
|
|
|
|
label are still under consideration, and efforts to implement such a proposal
|
|
|
|
|
have a high risk of being wasted. If you are interested in a proposal which is
|
|
|
|
|
still under consideration, please express your interest in the issue tracker,
|
|
|
|
|
providing extra insights and considerations that others have not yet expressed.
|
|
|
|
|
The most highly regarded argument in such a discussion is a real world use case.
|
2020-09-11 19:30:21 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
For more tips, please see the
|
|
|
|
|
[Contributing](https://github.com/ziglang/zig/wiki/Contributing) page on the
|
|
|
|
|
wiki.
|
2020-09-11 19:30:21 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
## Community
|
2020-09-11 19:30:21 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
The Zig community is decentralized. Anyone is free to start and maintain their
|
|
|
|
|
own space for Zig users to gather. There is no concept of "official" or
|
|
|
|
|
"unofficial". Each gathering place has its own moderators and rules. Users are
|
|
|
|
|
encouraged to be aware of the social structures of the spaces they inhabit, and
|
|
|
|
|
work purposefully to facilitate spaces that align with their values.
|
2020-10-22 03:55:35 +01:00
|
|
|
|
2023-07-23 23:48:54 +01:00
|
|
|
Please see the [Community](https://github.com/ziglang/zig/wiki/Community) wiki
|
|
|
|
|
page for a public listing of social spaces.
|
