Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

proton: Populate NVIDIA_WINE_DLL_DIR when available#8087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
liam-middlebrook wants to merge2 commits intoValveSoftware:experimental_9.0
base:experimental_9.0
Choose a base branch
Loading
fromliam-middlebrook:lmiddlebrook/nvidia-wine-dll-dir-env

Conversation

@liam-middlebrook
Copy link
Contributor

NVIDIA-software may check the environment variableNVIDIA_WINE_DLL_DIR for a path where DLLs provided by the NVIDIA Linux driver can be found. This needs to be set byproton script, as it is ran inside of the pressure-vessel environment, so the paths returned will be valid within the environment.

Tested with an application that readsNVIDIA_WINE_DLL_DIR from the environment and tries to load a known DLL from it. As expected manually setting the environment variable to the on-disk location did not work, as the path is not accurate within the pressure-vessel environment.

AlexeySFdot and ghishadow reacted with thumbs up emoji
Plagman pushed a commit that referenced this pull requestSep 10, 2024
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`for a path where DLLs provided by the NVIDIA Linux driver can be found.This needs to be set by `proton` script, as it is ran inside of thepressure-vessel environment, so the paths returned will be valid withinthe environment.Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from theenvironment and tries to load a known DLL from it. As expected manuallysetting the environment variable to the on-disk location did not work,as the path is not accurate within the pressure-vessel environment.#8087
Copy link

@adamdmossadamdmoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

For what my ex-nvidia-employee opinion is worth: LGTM. I infer from the lack of specifics (and not privileged knowledge) that this is to enable some future tech work, but if there is an existing title which needs this then pointing it out would be good for verification purposes.

@liam-middlebrook
Copy link
ContributorAuthor

Noting from a side-discussion between myself@ivyl, pgofman, and zf. This environment variable isn't ideal because it creates wine/proton specific behavior. Since the way this would be read on Windows isn't currently supported in Wine, this environment variable will only be read as a fallback. That way, in the future if the primary path is supported, this logic could be removed.

In the meantime there's some cleanup things to do here (like avoiding running through the C_DLL logic twice).

NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`for a path where DLLs provided by the NVIDIA Linux driver can be found.This is done as a fallback for when the "DriverStore" cannot be detectedvia the D3DDDI functions for querying an adapter-specific registry key.Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from theenvironment and tries to load a known DLL from it. As expected manuallysetting the environment variable to the on-disk location did not work,as the path is not accurate within the pressure-vessel environment.
@liam-middlebrookliam-middlebrookforce-pushed thelmiddlebrook/nvidia-wine-dll-dir-env branch from34e90a8 tod380d66CompareSeptember 19, 2024 04:29
@PlagmanPlagmanforce-pushed theexperimental_9.0 branch 3 times, most recently from124cdc3 to2a4943dCompareOctober 1, 2024 18:22
vinifmor pushed a commit to vinifmor/Proton that referenced this pull requestOct 3, 2024
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`for a path where DLLs provided by the NVIDIA Linux driver can be found.This needs to be set by `proton` script, as it is ran inside of thepressure-vessel environment, so the paths returned will be valid withinthe environment.Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from theenvironment and tries to load a known DLL from it. As expected manuallysetting the environment variable to the on-disk location did not work,as the path is not accurate within the pressure-vessel environment.ValveSoftware#8087
@PlagmanPlagmanforce-pushed theexperimental_9.0 branch 2 times, most recently from5d2111a to7f6b0ffCompareOctober 7, 2024 17:08
Plagman pushed a commit that referenced this pull requestNov 6, 2024
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`for a path where DLLs provided by the NVIDIA Linux driver can be found.This is done as a fallback for when the "DriverStore" cannot be detectedvia the D3DDDI functions for querying an adapter-specific registry key.Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from theenvironment and tries to load a known DLL from it. As expected manuallysetting the environment variable to the on-disk location did not work,as the path is not accurate within the pressure-vessel environment.Link:#8087
Plagman pushed a commit that referenced this pull requestNov 27, 2024
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`for a path where DLLs provided by the NVIDIA Linux driver can be found.This is done as a fallback for when the "DriverStore" cannot be detectedvia the D3DDDI functions for querying an adapter-specific registry key.Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from theenvironment and tries to load a known DLL from it. As expected manuallysetting the environment variable to the on-disk location did not work,as the path is not accurate within the pressure-vessel environment.Link:#8087
@PlagmanPlagmanforce-pushed theexperimental_9.0 branch 2 times, most recently from1753216 todcf29c3CompareDecember 24, 2024 20:37
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

1 more reviewer

@adamdmossadamdmossadamdmoss approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@liam-middlebrook@adamdmoss

[8]ページ先頭

©2009-2025 Movatter.jp