Please reference the actual license terms. I would also recommend
obtaining legal advice before going to market.
This excerpt from
https://www.gnu.org/licenses/gpl-faq.html#MereAggregation might help you:
"...By contrast, pipes, sockets and command-line arguments are
communication mechanisms normally used between two separate
programs. So when they are used for communication, the modules
normally are separate programs. But if the semantics of the
communication are intimate enough, exchanging complex internal data
structures, that too could be a basis to consider the two parts as
combined into a larger program."
- James Heliker
On 3/28/2015 1:00 AM, Carl Eugen Hoyos wrote:
Juan Urrego <libreacceso <at> ymail.com> writes:
Hi, I'm currently developing a commercial software product,
and I would like to know if there are any legal problems
with licenses
I don't know what "problems" mean in this context but if
you plan to distribute FFmpeg (that means software based on
FFmpeg source code), you have to conform to the GPL or the
LGPL (depending on how you compiled FFmpeg).
If you want to use FFmpeg, you have to agree with the
No-Warranty clause of the GPL (or the LGPL).
or patents
We do not know anything about patents (we have not used
patents to implement FFmpeg), so we cannot answer this
question but please see:
http://ffmpeg.org/legal.html
if I make my software compatible with FFmpeg.
I do not plan to distribute the ffmpeg.exe file
In case you neither use nor distribute software based
on FFmpeg source code, then what you do does not concern
the FFmpeg developers.
Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
_______________________________________________
ffmpeg-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
