[patch] qlibrary_win.cpp

Holger Schroeder holger-kde at holgis.net
Tue Oct 14 12:52:50 CEST 2003


Hi,

i think i talked about this before...

after my understanding we cannot allow anybody to use our code under a 
different license than the gpl one.
if we leave the tt license attributes in, we would for example allow 
commercial x11-only licensees to use qt on windows commercially with their 
x11 only licenses. i think we cannot allow anybody to do anything with the 
code, that is not bound to the gpl, so i removed all tt license statements in 
the _win classes.
perhaps i forgot some, but that was my intention.

i would recommend to continue in that way, to be on the safe side.

Holger

On Friday 10 October 2003 16:23, Andy Goossens wrote:
> On Friday 10 October 2003 00:24, Thiago A. Corrêa wrote:
> > For filenames ( and most other calls ) it's fine to use the A version...
> > as long as you don't use unicode characters in the filenames... ie,
> > writting them in russian or japanese hiragana. To handle those correctly,
> > we should do sth like:
> >
> > QT_WA( LoadLibraryA( filename.latin1() ) , LoadLibraryW(
> > filename.ucs2() ) );
>
> Hmmm... I tried that. The latin1() works fine, but the ucs2() doesn't.
> Compiler complains with:
>
> passing `const short unsigned int *' as argument 1 of (...) const WCHAR *
>
> > But that's not the only place where there will be issues... I fixed some
> > myself from kde-cygwin's version merging them into mine ( as I have
> > UNICODE defined by default )
>
> You might want to send a patch fixing those issues after the Qt update :-)
>
> > About license: I belive we can choose to only release the _win.cpp under
> > GPL... the rest says that ppl who own a TT license can produce commercial
> > stuff... I belive those who do have a license won't want our "bugged
> > version" *smile*. But I guess it would be nice to TT if we keep their
> > same license, allowing those with a license from TT to produce commercial
> > apps,
>
> For the moment being I would say we keep GPL and QPL in there, unless
> complications turn up. I'm wondering what TT thinks about commercial apps
> using our port.



More information about the kde-cygwin mailing list