NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

DXVK-Remix build fails due to missing meson.build files

Open
#923 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

jira
Dominant language
No language data
Stars
1.7k
Forks
99
PR merge metrics
No merged PRs in 30d

Description

DXVK-Remix build fails due to missing meson.build files

Description

DXVK-Remix build fails due to nonexistent build file tests/rtx\dxvk_rt_testing\meson.build. If you delete the dxvk_rt_testing directory, sometimes the nv-private folder generates and causes the build to fail due to nonexistent build file nv-private\meson.build.

This appears to have been introduced in commit 74608c34cbc0a8919b032e17b3563e7097aba4f9 on DXVK-Remix repo.

Note: This issue appears to only happen on certain systems

Steps to Reproduce

  1. Clone the repository and attempt to build using dxvk-remix\build_dxvk_all_ninja.ps1
  2. Build fails with error about missing tests/rtx/dxvk_rt_testing/meson.build
  3. After manually deleting the dxvk_rt_testing directory, build may fail again with error about missing nv-private/meson.build

Expected Behavior

Build should complete successfully without requiring manual deletion of directories or encountering missing meson.build files.

Actual Behavior

Build fails due to missing meson.build files in the tests/rtx/dxvk_rt_testing subdirectories.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with dxvk-remix\build_dxvk_all_ninja.ps1 and reproduce the failure involving tests/rtx/dxvk_rt_testing/meson.build. Compare the generated or checked-out directories with commit 74608c34cbc0a8919b032e17b3563e7097aba4f9, including the possible nv-private\meson.build failure. Done means the build completes without manual directory deletion on the affected systems.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.