feat(cmake): use symlink/junction for shaders in build dir

[ns6089]

Description

Use directory junction instead of copy in the build directory during cmake configure on Windows.
This prevents work-in-progress shaders getting overwritten without any confirmation.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[ReenigneArcher]

Same changes also needed for Linux.

Sunshine/cmake/packaging/linux.cmake

Lines 5 to 7 in 2996727

	# copy assets to build directory, for running without install
	file(COPY "${SUNSHINE_SOURCE_ASSETS_DIR}/linux/assets/"
	DESTINATION "${CMAKE_BINARY_DIR}/assets")

[ns6089]

Same changes also needed for Linux.

I wouldn't say needed. but I can make them. But I can't say for sure that it won't break some obscure build configuration or packager, unlike windows on linux copying symlinks copy symlinks themselves, not what they point at.

@ReenigneArcher so in light of this information, should I do it or not?

[ReenigneArcher]

I wouldn't say needed

Right, it could just be annoyance when developing on Linux, just like it was for you on Windows. Shouldn't affect anything for packagers as I only added this for allowing unit tests to run without doing a full blown install.

should I do it or not?

Yes, please.

[ns6089]

Added shaders directory symlink to linux cmake.
Untested, but if CI doesn't fail it should work fine.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 9.69%. Comparing base (0a6abb7) to head (d75bc3a).
Report is 128 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #3013    +/-   ##
=======================================
  Coverage    9.69%   9.69%            
=======================================
  Files         101     101            
  Lines       17913   17913            
  Branches     8376    8376            
=======================================
  Hits         1736    1736            
+ Misses      13453   13313   -140     
- Partials     2724    2864   +140     

Flag	Coverage Δ
Linux	7.31% <ø> (ø)
Windows	5.06% <ø> (ø)
macOS-12	10.50% <ø> (ø)
macOS-13	10.42% <ø> (ø)
macOS-14	10.73% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 31 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles