customization.cfg

# vkd3d-git-tkg config file

# External config file to use - If the given file exists in path, it will override default config (customization.cfg) - Default is ~/.config/frogminer/vkd3d-git.cfg
_EXT_CONFIG_PATH=~/.config/frogminer/vkd3d-git.cfg

# custom vkd3d commit to pass to git
_vkd3d_commit=""

# vkd3d source - leave empty for stock (https://source.winehq.org/git/vkd3d.git), or set a custom repository.
# Using `https://github.com/HansKristian-Work/vkd3d-proton` can prevent wine compilation due to upstream changes breaking compat and is not recommended as a result unless you know what you're doing. For vkd3d-proton, it's recommended to use a standalone build you can get with https://github.com/Frogging-Family/dxvk-tools.
_vkd3d_source=""

# set to true to use the autotools build system instead of meson when using vkd3d fork (https://github.com/HansKristian-Work/vkd3d-proton)
_fork_disable_meson="false"

# Custom compiler root dirs - Leave empty to use system compilers
# Example: CUSTOM_GCC_PATH="/home/frog/PKGBUILDS/mostlyportable-gcc/gcc-mostlyportable-9.2.0"
CUSTOM_GCC_PATH=""


#### USER PATCHES ####

# community patches - add patches (separated by a space) of your choice by name from the community-patches dir
# example: _community_patches="secret-of-the-plagman.myvkd3dpatch wow-flicker-fix.myvkd3dpatch"
_community_patches=""

# You can use your own patches by putting them in the same folder as the PKGBUILD and giving them the .myvkd3dpatch extension.
# You can also revert patches by putting them in the same folder as the PKGBUILD and giving them the .myvkd3drevert extension.

# Apply all user patches without confirmation - !!! NOT RECOMMENDED !!!
_user_patches_no_confirm="false"