void-packages/common/build-style/zig-build.sh

do_build() {
	local zig_target zig_cpu

	# TODO: This duplication between build-profiles and cross-profiles
	# is totally unnecessary. It would be nice if there was some way to
	# avoid it.
	if [ "$CROSS_BUILD" ]; then
		zig_target="${XBPS_CROSS_ZIG_TARGET}"
		zig_cpu="${XBPS_CROSS_ZIG_CPU}"
	else
		zig_target="${XBPS_ZIG_TARGET}"
		zig_cpu="${XBPS_ZIG_CPU}"
	fi

	# Inform zig of the required libc include paths.
	cat > xbps_zig_libc.txt <<-EOF
		include_dir=${XBPS_CROSS_BASE}/usr/include
		sys_include_dir=${XBPS_CROSS_BASE}/usr/include
		crt_dir=${XBPS_CROSS_BASE}/usr/lib
		msvc_lib_dir=
		kernel32_lib_dir=
		gcc_dir=
	EOF

	# The Zig build system only has a single install step, there is no
	# way to build artifacts for a given prefix and then install those artifacts
	# to that prefix at some later time. Therefore, we build and install to the zig-out
	# directory and later copy the artifacts to the destdir in do_install().
	# We use zig-out to avoid path conflicts as it is the default install
	# prefix used by the zig build system.
	DESTDIR="zig-out" zig build \
		-j"${XBPS_MAKEJOBS}" \
		--sysroot "${XBPS_CROSS_BASE}" \
		--search-prefix "${XBPS_CROSS_BASE}/usr" \
		--prefix /usr \
		--global-cache-dir /host/zig \
		--libc xbps_zig_libc.txt \
		--release=safe \
		--verbose \
		-Dtarget="${zig_target}" -Dcpu="${zig_cpu}" \
		install \
		${configure_args}
}

do_install() {
	cp -r zig-out/* "${DESTDIR}"
}