From: "Marco Costalba" <mcostalba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [RFC] Distributing Windows binary package compiled with non gpl code
Date: Thu, 27 Dec 2007 19:32:09 +0100 [thread overview]
Message-ID: <e5bfff550712271032q25d135e7y47d68337e937d401@mail.gmail.com> (raw)
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 !
next reply other threads:[~2007-12-27 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 18:32 Marco Costalba [this message]
2007-12-27 22:08 ` [RFC] Distributing Windows binary package compiled with non gpl code Daniel Barkalow
2007-12-27 23:10 ` Abdelrazak Younes
2007-12-28 0:05 ` Daniel Barkalow
2007-12-28 8:17 ` Marco Costalba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5bfff550712271032q25d135e7y47d68337e937d401@mail.gmail.com \
--to=mcostalba-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).