-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(cmake): copy asset files to build dir #2338
build(cmake): copy asset files to build dir #2338
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## nightly #2338 +/- ##
=======================================
Coverage 6.10% 6.10%
=======================================
Files 85 85
Lines 18303 18303
Branches 8319 8319
=======================================
Hits 1118 1118
- Misses 15362 15374 +12
+ Partials 1823 1811 -12
Flags with carried forward coverage won't be shown. Click here to find out more. |
2cdc6c1
to
7713b5b
Compare
@FrogTheFrog I think you asked about this before, if you want to give it a try. |
No, it was about: Sunshine/cmake/targets/common.cmake Line 55 in 1329c51
|
I don't have bash on Windows... |
Okay, that is actually another issue I'm facing. While I do have bash, for some reason on CLion it finds very old versions of npm and node, but I can't reproduce it in any of my shells manually. In any event, this PR makes it so you can execute the built binary, without doing an "install" or copying any files manually to the build directory. |
Description
This PR makes a change to the build process, where asset files are copied to the build directory, so that the generated binary can be run without an install. This is mostly to improve the development process, although some users have wanted to run Sunshine without an install in the past as well.
This uses the
file(COPY ...)
method which actually copies the files when running cmake, before the build.Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.