Re:Show HN: I completed shipping my desktop app
by newusertoday on Saturday January 04, 2025 @12:17AM
(#42592626)
how are you able to get around ffmpeg licensing since it is client app which requires you to open your code if you use ffmpeg GPL?
[ Parent
| on HN ]
Re:Show HN: I completed shipping my desktop app
by fourthark on Saturday January 04, 2025 @01:18AM
(#42592856)
FFmpeg is mostly LGPL and has very clear and helpful instructions about how to incorporate and distribute it in compliance.
Re:Show HN: I completed shipping my desktop app
by levkk on Saturday January 04, 2025 @12:28AM
(#42592684)
It does not require that you do that. It only requires you to open source any modifications you've made to ffmpeg.
Re:Show HN: I completed shipping my desktop app
by newusertoday on Saturday January 04, 2025 @01:19AM
(#42592863)
it is slightly more nuanced, if you do static linking it is considered derivative work and does requires you to open it. Since the app is based on ffmpeg which is GPL(core is LGPL) i am curious to know how it is getting used.
Re:Show HN: I completed shipping my desktop app
by anshrathodfr on Saturday January 04, 2025 @01:36AM
(#42592940)
i didn't bundle the ffmpeg in the app. It uses homebrew to install ffmpeg on the user's device. this is the acceptable way since ffmpeg confirms it on twitter/X.
Re:Show HN: I completed shipping my desktop app
by p4bl0 on Saturday January 04, 2025 @08:05AM
(#42594462)
This tweet also explicitly says "But still would be nice to have some credit.".
Why isn't FFmpeg mentioned on your app's website?
The same goes for ImageMagick by the way.
Re:Show HN: I completed shipping my desktop app
by anshrathodfr on Sunday January 05, 2025 @03:20AM
(#42600464)
there is a dedicated page for credits: https://pimosa.app/credits
Re:Show HN: I completed shipping my desktop app
by kiritanpo on Saturday January 04, 2025 @08:47AM
(#42594649)
Static linking of LGPL content (thus making it derivative work) only requires that it must allow "modification of the work for the customer's own use and reverse engineering for debugging such modifications".
Making your own code public is not the only way to achieve this.
You can also make available to customer object files and build instructions to recreate your software with the (modified) statically linked LGPL content. (if it's LGPL > 2.1 you have extra requirements: you need to provide all toolchains/dependencies and it must be actually possible to install a modified version on the hardware)
Granted, this is not commonly used but I've used this on some projects where dynamic linking was not available/desired by client.
Re:Show HN: I completed shipping my desktop app
by anshrathodfr on Saturday January 04, 2025 @01:33AM
(#42592931)
it uses homebrew to install the FFmpeg on the user's device. the app doesn't bundle any libs to comply with their license limitations.
Re:Show HN: I completed shipping my desktop app
by globalnode on Saturday January 04, 2025 @12:25AM
(#42592669)
O_o, well that was a short lived app.
Re:Show HN: I completed shipping my desktop app
by odo1242 on Saturday January 04, 2025 @02:27AM
(#42593139)
FFmpeg is LGPL, not GPL. This means that you can link it in non open source apps and only have to open source modifications to FFmpeg itself.
Re:Show HN: I completed shipping my desktop app
by rane on Saturday January 04, 2025 @07:32AM
(#42594332)
It doesn't if you use it as a bundled binary.
https://opensource.stackexchange.com/questions/4008/can-i-us...
https://opensource.stackexchange.com/questions/5188/software...