-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Sunshine prebuilts #510
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
Sunshine prebuilts #510
Conversation
Note that you can remove references to |
04c9942
to
dec65b8
Compare
dec65b8
to
c9c8c45
Compare
@ReenigneArcher @brad-richardson I think that sunshine should be dynamically linked to distribution-provided dependencies whenever possible, especially when doing custom build (like AUR). It would be better to only use prebuilts when the distribution-provided dependencies are unavailable. |
With this PR merged, Sunshine is still configured as a dynamic binary for everything except the ffmpeg libraries. Static builds of the latter are useful not only due to variances in ffmpeg versions between distributions, but also because we need custom patches to the ffmpeg source in order to fix issues with certain encoders.
|
There is no license file in https://github.com/LizardByte/build-deps, which may violate the licenses of these libraries. |
Yes, a license file should be added. Can you point me to more information re: royalties for static builds? The x265 source appears to be GPL2, and we have not modified or withheld any source modifications. |
@psyke83 Is it possible to publish these patches, or even write a script to allow locally building these libraries and linking them with sunshine easily? |
The patches are here: https://github.com/LizardByte/build-deps/tree/master/ffmpeg_patches/ffmpeg The build procedure is done via a github workflow, but it can be reproduced locally. See: https://github.com/LizardByte/build-deps/blob/master/.github/workflows/build-ffmpeg.yml |
@psyke83 It is all about patent. H264 and H265 are patent protected. Using it with FOSS may be acceptable but is indeed questionable. |
@psyke83 I see that most linux distros package |
While I think this requires more research - and the missing license file definitely needs addressing - I'm not convinced that there's additional risk in statically linking x265. The official ffmpeg site links to static builds of ffmpeg here: https://johnvansickle.com/ffmpeg/ Those builds are licensed as GPL3, and I verified that libx264 and libx265 are present with no dynamic linking whatsover. Note that I'm only a contributor to this repo, so please don't interpret my opinion here as reflecting the project. |
The royalties of MPEG-LA are based on units sold. No units sold, means no royalties. Also x265 is not the same as H265. |
Description
Use new ffmpeg prebuilts across all platforms, provides library consistency and preps for ffmpeg5 upgrade.
Issues Fixed or Closed
Type of Change
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.