[RFC] Distributing Windows binary package compiled with non gpl code
- From
- Marco Costalba <mcostalba-re5jqeeqqe8avxtiumwx3w@public.gmane.org>
- Date
- Dec 27, 2007, 18:32 UTC
- Message-ID
- <e5bfff550712271032q25d135e7y47d68337e937d401@mail.gmail.com>
It seems I have finally worked out a binary installation of qgit under Windows:
http://digilander.libero.it/mcostalba/qgit2.1rc1_win.exe
It seems to work with msysgit distribution of git. It DOES NOT work as expected with Cygwin git that IMHO is very broken for qgit. I ended up giving the blame to mingw, but after testing the MSVC compiled qgit both with msysgit and cygwin git I have to say that the problem *probably* is not in mingw but in cygwin.
Anyhow the MSVC 2008 compiled qgit seems stable and works as advertised. Now that's the question:
Packaged together with qgit.exe there are the necessary Micorsoft Visual C dll's. Is this a problem for someone?
I could try to compile again everything with mingw and test if under msysgit the artifacts that appear with cygwin are fixed, if this succeed I could prepare a binary package built with mingw and distribute this instead, but would be this necessary?
qgit is GPL and I for sure want to be stick to GPL, so I don't know if this can be an issue.
Thanks for help me in clarifing this point
Marco
P.S: Just to be fair I have to say that developing under Windows with MSVC is much easier, because the debugging tools available with MSVC 2008 are very advanced and powerful, nothing similar exists _for Window_ in the GPL camp. Indeed MSVC (together with SQL Server) are (the only) two good products from MS, so good that even do not seem produced by Microsoft !