fix docs
parent
6c3a56a7ff
commit
79400bfdfd
|
@ -106,13 +106,20 @@ libc. Create demo games using Zig.
|
|||
These compile tools must be available on your system and are used to build
|
||||
the Zig compiler itself:
|
||||
|
||||
##### POSIX
|
||||
|
||||
* gcc >= 5.0.0 or clang >= 3.6.0
|
||||
* cmake >= 2.8.5
|
||||
|
||||
##### Windows
|
||||
|
||||
* Microsoft Visual Studio 2015
|
||||
|
||||
#### Library Dependencies
|
||||
|
||||
These libraries must be installed on your system, with the development files
|
||||
available. The Zig compiler links against them.
|
||||
available. The Zig compiler links against them. You have to use the same
|
||||
compiler for these libraries as you do to compile Zig.
|
||||
|
||||
* LLVM, Clang, and LLD libraries == 5.x
|
||||
|
||||
|
|
|
@ -6,8 +6,8 @@ choose to add more files to the compilation, for example bootstrap.zig which
|
|||
contains the code that calls main.
|
||||
|
||||
Our goal now is to treat everything that is marked with the `export` keyword
|
||||
as a root node, and then then parse and semantically analyze as little as
|
||||
possible in order to fulfill these exports.
|
||||
as a root node, and then parse and semantically analyze as little as possible
|
||||
in order to fulfill these exports.
|
||||
|
||||
So, some parts of the code very well may have uncaught semantic errors, but as
|
||||
long as the code is not referenced in any way, the compiler will not complain
|
||||
|
|
Loading…
Reference in New Issue