zig/src/config.zig.in

pub const have_llvm = true;
pub const llvm_has_m68k = false;
pub const llvm_has_csky = false;
pub const llvm_has_arc = false;
pub const version: [:0]const u8 = "@ZIG_VERSION@";
pub const semver = @import("std").SemanticVersion.parse(version) catch unreachable;
pub const enable_logging: bool = @ZIG_ENABLE_LOGGING_BOOL@;
pub const enable_link_snapshots: bool = false;
pub const enable_tracy = false;
pub const value_tracing = false;
pub const have_stage1 = true;
pub const skip_non_native = false;
pub const only_c = false;
start moving `zig cc` to stage2 * build.zig: repair the ability to link against llvm, clang, and lld * move the zig cc arg parsing logic to stage2 - the preprocessor flag is still TODO - the clang arg iterator code is improved to use slices instead of raw pointers because it no longer has to deal with an extern struct. * clean up error printing with a `fatal` function and use log API for messages rather than std.debug.print * add support for more CLI options to stage2 & update usage text - hooking up most of these new options is TODO * clean up the way libc and libc++ are detected via command line options. target information is used to determine if any of the libc candidate names are chosen. * add native library directory detection * implement the ability to invoke clang from stage2 * introduce a build_options.have_llvm so we can comptime branch on whether LLVM is linked in or not. 2020-09-04 04:23:00 +01:00			`pub const have_llvm = true;`
stage2: update LLVM backend to for LLVM 13 There was some new code in master branch enumerating all the targets and a new target was added so we needed to add the glue code. This commit also introduces some build options to support experimental LLVM targets. 2021-09-01 06:50:10 +01:00			`pub const llvm_has_m68k = false;`
			`pub const llvm_has_csky = false;`
			`pub const llvm_has_arc = false;`
restore the option to build with cmake restore cmake to be capable of figuring out the zig version restore config.h and config.zig. config.h is used to detect whether we should propagate cmake configuration information to build.zig; however it can be overridden with -Dstatic-llvm. fix not passing -DZIG_LINK_MODE with zig build. when using the cmake build path, build.zig no longer tries to call llvm-config. Instead it relies 100% on the LLVM_LIBRARIES cmake variable. build.zig logic reworked and simplified. 2020-12-08 00:23:17 +00:00			`pub const version: [:0]const u8 = "@ZIG_VERSION@";`
add ast-check flag to zig fmt, fix found bugs 2021-06-13 20:27:27 +01:00			`pub const semver = @import("std").SemanticVersion.parse(version) catch unreachable;`
stage1: add cmake flag for enabling logging Now that we ship our own linker for MachO by default in both stage1 and stage2, we need a way to enable logs for verbose debugging. This commit adds `ZIG_ENABLE_LOGGING` cmake option which is equivalent to stage2's `-Dlog` flag. To enable it when building stage1 with cmake, add: ``` cmake .. -DZIG_ENABLE_LOGGING=on ``` 2021-03-21 09:56:41 +00:00			`pub const enable_logging: bool = @ZIG_ENABLE_LOGGING_BOOL@;`
macho: dump linker's state as JSON Each element of the output JSON has the VM address of the generated binary nondecreasing (some elements might occupy the same VM address for example the atom and the relocation might coincide in the address space). The generated JSON can be inspected manually or via a preview tool `zig-snapshots` that I am currently working on and will allow the user to inspect interactively the state of the linker together with the positioning of sections, symbols, atoms and relocations within each snapshot state, and in the future, between snapshots too. This should allow for quicker debugging of the linker which is nontrivial when run in the incremental mode. Note that the state will only be dumped if the compiler is built with `-Dlink-snapshot` flag on, and then the compiler is passed `--debug-link-snapshot` flag upon compiling a source/project. 2021-10-14 12:50:10 +01:00			`pub const enable_link_snapshots: bool = false;`
simplify `zig info` and rename it to `zig env` also add version to it 2020-08-18 01:06:23 +01:00			`pub const enable_tracy = false;`
stage2: use std.debug.Trace only when explicitly enabled Because it bumps up the stack space requirements, which is making a test case fail on aarch64 drone CI. 2022-06-09 23:33:04 +01:00			`pub const value_tracing = false;`
make self-hosted the default compiler stage1 is available behind the -fstage1 flag. closes #89 2022-08-08 07:10:57 +01:00			`pub const have_stage1 = true;`
stage2: wire up -Dskip-non-native The purpose of this is to save time in the edit-compile-test cycle when working on stage2 code. 2020-12-02 21:51:22 +00:00			`pub const skip_non_native = false;`
build: add `-Donly-c` option This option can be used to produce a C backend build of the self-hosted compiler, which only has the C backend enabled. Once the C backend is capable of self-hosting, this will be a way for us to replace our stage1 codebase with a C backend build of self-hosted, which we can then use for bootstrapping. See #5246 for more details. Using this option right now results in a crash because the C backend is not yet passing all the behavior tests. 2022-10-23 21:18:22 +01:00			`pub const only_c = false;`