You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fine-grained management/naming: wsl-lib is added to hardware.graphics.extraPackages immediately upon creation here. It should be ensured that all items within are graphics libraries. After ensuring this, wsl-lib should be renamed to wsl-graphics-lib or wsl-lib.graphics.
Current version does not link all files: This is the code submitted two years ago. Since then, it seems that libnvidia-gpucomp.so, libnvidia-ngx.so.1, and nvidia-ngx-updater have been added. These should be included.
2.1: Should circular linking be considered: (The difficulty mentioned in Add NVIDIA acceleration how-to documentation #586 (comment)) Although the comment indicates that /usr/lib/wsl/lib cannot be directly linked, would circular linking be a better solution to avoid the issue in point 2?
This issue involves:
/usr/lib/wsl/libwsl-lib
#578
#586
Problem
wsl-libis added tohardware.graphics.extraPackagesimmediately upon creation here. It should be ensured that all items within are graphics libraries. After ensuring this,wsl-libshould be renamed towsl-graphics-liborwsl-lib.graphics.libnvidia-gpucomp.so,libnvidia-ngx.so.1, andnvidia-ngx-updaterhave been added. These should be included.2.1: Should circular linking be considered: (The difficulty mentioned in Add NVIDIA acceleration how-to documentation #586 (comment)) Although the comment indicates that
/usr/lib/wsl/libcannot be directly linked, would circular linking be a better solution to avoid the issue in point 2?nix-ld. It might also be needed in other scenarios.nix-ld: After enablinguseWindowsDriver, it should be automatically added tonix-ld.