Alex Cohn writes:
> PS I often find the reactions to licensing questions on this and other
> open software lists intimidating. I believe that open software should
> (pun intended) be promoted, among other ways, by making it easier to
> understand and use, even at risk of somebody unintentionally
On Tue, Dec 6, 2011 at 23:14, Carl Eugen Hoyos wrote:
>> Yes, you should provide the source code with any build scripts you use.
>
> I am not a native speaker but I wonder if the word "should" (here and below)
> is
> the right choice...
Correct, my usage of the word "should" was absolutely info
Alex Cohn writes:
> On Mon, Dec 5, 2011 at 12:30, kunkka cai wrote:
> > Hi,
> > I'm developing a free (in price) software which should be able to play mp3
> > files. I know ffmpeg is a great codec, so I want my application to link
> > against it.
> > Actually I have built some Dlls (avcodec-52.d
On Mon, Dec 5, 2011 at 12:30, kunkka cai wrote:
> Hi,
> I'm developing a free (in price) software which should be able to play mp3
> files. I know ffmpeg is a great codec, so I want my application to link
> against it.
> Actually I have built some Dlls (avcodec-52.dll, avformat-52.dll,
> avutil-50
Look at the section *License Compliance Checklist:*
http://ffmpeg.org/legal.html
I think it answers your questions :)
Cheers
On Mon, Dec 5, 2011 at 11:30 AM, kunkka cai wrote:
> Hi,
> I'm developing a free (in price) software which should be able to play mp3
> files. I know ffmpeg is a great c
Hi,
I'm developing a free (in price) software which should be able to play mp3
files. I know ffmpeg is a great codec, so I want my application to link
against it.
Actually I have built some Dlls (avcodec-52.dll, avformat-52.dll,
avutil-50.dll) without "--enable-gpl" and without "--enable-nofree".
