Warren Young wrote:
> > On May 22, 2008, at 1:52 PM, support wrote:
> >
>
>> >> I'm evaluating mysql++ and I would like to create a closed source app
>> >> using it. Likely it would stay in house but we need to be able to
>> >> distribute it in the future if we should decide to do so. As long as we
>> >> link dynamically, this is possible, correct?
>>
> >
> > IANAL, and I don't speak for any other entity, not even the company I
> > work for. My informed opinion is, "yes". :)
> >
>
>> >> Can we distribute the mysql++ .dll/.so binary with our application?
>>
> >
> > Yes, as long as you're willing to provide the source code that
> > produced that DLL to anyone who asks. The exact terms of this
> > requirement are spelled out in the LGPL.
> >
>
>> >> Same question for the mysql C api .dll/.so..?
>>
> >
> > The MySQL C API is under the GPL, not the LGPL, so it doesn't matter
> > how you link: your app falls under the GPL unless you buy a commercial
> > redistribution license from MySQL, Inc.
> >
>
oops, sorry I reponded to you and not list..
Now i'm confused. mysql++ isn't much use without the mysql C api... So
it really IS NOT possible to do what I want, unless I buy a license from
MySQL? I cannot open-source this app.
Wait, maybe you misunderstood my second question. ok:
I want to create a closed source app. I want to use mysql++. I don't link to mysql C api
or touch it, but mysql++ does.
I want to include the mysql++ dll and the mysql C api dll with my app when I
distribute it so it 'just works'. I don't mind making the source for
those available if I have to. I will not allow any of my code to become
GPL or LGPL. I do not want to spend money. Is it possible?
If not, what about the mysql ODBC connector?
