digger.ini.sample

# Copy this file to digger.ini, and make the appropriate
# changes below.

# Digger looks for digger.ini in these locations, in order:
# - current directory
# - EXE directory
# - source directory
# - On POSIX:
#   - $XDG_CONFIG_HOME/digger/ (default ~/.config/digger/)
#   - $XDG_CONFIG_DIRS/digger/ (default /etc/xdg/digger/)
# - On Windows:
#   - %APPDATA%\Digger\
#     (default C:\Users\<username>\AppData\Roaming\Digger)
#
# Additionally, for compatibility with previous versions,
# the following locations are searched:
# - ~/.digger/digger.ini
# - On POSIX: /etc/digger.ini.

# Syntax:
# The section names define an implicit prefix, thus ...
#   [a.b]
#   c.d=e
# ... is equivalent to ...
#   a.b.c.d=e

# These settings can also be set from the command line using
# the -c option, and also overridden in a bisect.ini file,
# e.g.: -c build.components.dmd.debugDMD=true

# Local configuration.

[local]

# Working directory.
# This directory will contain all of Digger's working files:
# the D repositories, any build prerequisites obtained
# automatically, the current build output, and the cache, if
# enabled.
# Please specify an absolute path. The default is to use the
# current directory.

#workDir = C:\Temp\Digger

# How many jobs to run makefiles in.
# Gets passed to GNU make as the -j parameter (not supported by
# DigitalMars make on Windows). Specify "auto" to use the
# CPU core count, or "unlimited" for no limit.
# Equivalent to the --jobs command-line option.

#makeJobs = auto

# Don't go online to fetch the latest revisions from GitHub.
# Equivalent to the --offline command-line switch.

#offline = false

# Build cache.
# To speed up successive runs, Digger can save the results of
# each commit's build. The downside is that this uses up disk
# space. The following cache engines are available:
# - none       No persistent cache.
# - directory  Store built files in a directory tree.
#              Saves some disk space by hard-linking identical
#              files.
# - git        Use a git repository (and git's deduplication /
#              compression mechanisms). Uses much less disk
#              space than "directory", but is a little slower.
# You can periodically run "digger compact" to optimize disk
# space used by the cache.

#cache = git

# Default build options.

[build]

# Enable or disable D components to build.
# For example, rdmd is rarely needed, so we can disable it here.
# Additional components not enabled by default can also be added.
# Equivalent to the --with and --without "digger build" options.
# Run `digger build --help` to see a list of available components.

#components.enable.rdmd = false

# Target model.
# Whether to target 32 or 64 bits when building D components.
# On Windows, 32mscoff is also an option.
# The default is to use the system model on POSIX, and 32-bit
# on Windows. Equivalent to the `digger build --model` option.
# Multiple models can be specified simultaneously by
# comma-separating them.

#components.common.model = 32,64

# Additional make parameters.
# Equivalent to the --make-args "digger build" option.

#components.common.makeArgs = ["HOST_CC=g++48"]

# Whether to build a debug compiler.
# Debug compilers are built quicker, but compile D code slower.

#components.dmd.debugDMD = false

# Whether to build a release compiler.
# Enables optimizations. Mutually exclusive with the above.

#components.dmd.releaseDMD = false

# Model for building DMD itself (on Windows).
# Can be used to build a 64-bit DMD, to avoid 4GB limit.
# Currently only implemented on Windows, for DMD 2.072 or later.
# Can also be set to 32mscoff.

#components.dmd.dmdModel = 64

# How to obtain a D compiler to build the parts of DMD written in D.

# Digger can either download a pre-built D version (default),
# or build one from source.
# Equivalent to the `digger build --bootstrap` option.

#components.dmd.bootstrap.fromSource = false

# Which D version to use when building the D compiler.
# The default is to select one automatically.
# This can be a version name, such as "v2.070.2",
# but also an arbitrary version specification
# (only when bootstrapping from source),
# as when using "digger build".

#components.dmd.bootstrap.ver = v2.067.1

# Build configuration for the compiler used for bootstrapping.
# If no options are set, the default settings are used,
# so specify any pertinent build settings that apply to both
# the host (bootstrapping) and built compiler here as well.
# Used when fromSource is true.

#components.dmd.bootstrap.build.option = value

# Note that it is possible to bootstrap the bootstrapping
# compiler, up to an arbitrary depth. For example, to build
# 2.067.1 from source, then use it to build master, then
# build master again using the compiler just built from master:

# $ digger \
# 	-c "build.components.dmd.bootstrap.build.components.dmd.bootstrap.fromSource = true" \
# 	-c "build.components.dmd.bootstrap.build.components.dmd.bootstrap.ver = v2.067.1" \
# 	-c "build.components.dmd.bootstrap.fromSource = true" \
# 	-c "build.components.dmd.bootstrap.ver = master" \
# 	build master

# Build/test environment.
# By default, Digger completely clears the environment and
# builds a new one from scratch, to avoid potential sources
# of contamination that can affect the D builds or test results.
[build.environment]

# You can use %VAR% syntax to refer to the previous value of a
# variable, or if there wasn't one, to the value from the
# original host environment (before it was cleared and rebuilt).

# Examples:

# Add something to PATH
#PATH=%PATH%;C:\Tools

# Import PATHEXT from the original environment
#PATHEXT=%PATHEXT%

# There are some additional lesser-used options not listed here,
# see ae.sys.d.manager.DManager.Config for details.