Clarify the language around building dxvk.

This commit is contained in:
Jeremy White 2018-08-21 19:19:13 -05:00
parent b8a3b24736
commit 87e0abda53

View File

@ -129,10 +129,10 @@ libraries in each chroot. Search for '<tt>executing Makefile commands</tt>' in
<tt>config.log</tt> to find messages about missing libraries. It is normal to be missing <tt>config.log</tt> to find messages about missing libraries. It is normal to be missing
a few libraries, including OpenCL, OSS, and libav. a few libraries, including OpenCL, OSS, and libav.
**NOTE:** For now, dxvk requires build-time components that are too new for **NOTE:** The build_proton.sh script builds most components inside the Steam runtime
Debian 9. It's recommended to build the DLLs on Arch Linux, where dxvk is chroot. However, dxvk will not build in that environment, so the build_proton.sh
actively being developed. This may be resolved in dxvk in the future, or may script will build it on your local system. This will require you to be able to
be worked around by using a newer Debian release. See comments in <tt>build_proton.sh</tt>. build dxvk on your local system; refer to [the dxvk README.md](https://github.com/ValveSoftware/dxvk/blob/master/README.md) for more details.
--- ---
Building for macOS Building for macOS