From: Abdelrazak Younes <younes.a-GANU6spQydw@public.gmane.org>
To: Marco Costalba <mcostalba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Johannes Schindelin
<Johannes.Schindelin-Mmb7MZpHnFY@public.gmane.org>,
msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Windows binaries for qgit 2.0
Date: Mon, 17 Dec 2007 22:40:30 +0100 [thread overview]
Message-ID: <4766ECCE.8010404@free.fr> (raw)
In-Reply-To: <e5bfff550712171114i40a59b11md87038a3fc13d29c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Marco Costalba wrote:
> On Dec 17, 2007 11:44 AM, Johannes Schindelin
> <Johannes.Schindelin-Mmb7MZpHnFY@public.gmane.org> wrote:
>
>> Why would anything that has to do with MSVC2005 be interesting to msysGit?
>> Note the "msys" part of "msysGit".
>>
>> FWIW a member of our team works on compiling/including qgit into msysGit.
>> But definitely not using closed-source compilers. I would violently
>> oppose that.
>>
>>
>
> I would (violently) agree with you, but I also violently oppose to
> waste a week end fighting with Qt4 + mingw compilation. MSVC2005 is
> needed as a kind of "debug tool" to better understand if the problem
> is with Qt4 or with mingw (as I suspect).
>
> Abdel is very kind to try to help in caming out with a qgit.exe more
> or less ready to be packaged. I'm not opposed, in this phase, to
> follow different _technically_ sound paths. Then when the dust settles
> down we could do our consideration regarding open source, in which I
> belive very firmly, so firmly that I'm not scared to _test_ different
> ways if this can be useful to shed some light on this issue.
>
If you allow me to share my experience in the LyX project WRT mingw/msys
versus MSVC: We tried very hard to use it, but at the end we faced many
issues, so many issues that MSVC was the only pragmatic choice:
- autotools hell with msys: the automake version was simply too old and
we had to mix cygwin and msys environment to get something done.
- linker hell: more than 500 megs of RAM was needed to link LyX with
Qt3, the situation was better with Qt4 but still.
- compilation slowness. Mingw is just not good with C++.
- binary slowness: this is less of a problem with Qt4 but still, the
MSVC compiled LyX is much faster.
In conclusion, I guess C-compilation is fine with Mingw and you should
definitly stay with it for git, but for a heavy GUI oriented C++ program
I strongly recommend MSVC.
Abdel.
next prev parent reply other threads:[~2007-12-17 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 15:02 Windows binaries for qgit 2.0 Marco Costalba
2007-12-16 7:26 ` Abdelrazak Younes
2007-12-16 7:55 ` Marco Costalba
2007-12-16 8:52 ` Abdelrazak Younes
2007-12-16 9:05 ` Marco Costalba
2007-12-16 9:10 ` Abdelrazak Younes
2007-12-16 10:42 ` Marco Costalba
2007-12-16 11:11 ` Abdelrazak Younes
2007-12-16 22:26 ` Marco Costalba
[not found] ` <e5bfff550712161426y101c77efl4f5321d3440fed3f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 9:51 ` Abdelrazak Younes
2007-12-17 10:44 ` [msysGit] " Johannes Schindelin
2007-12-17 11:07 ` Abdelrazak Younes
2007-12-17 19:14 ` Marco Costalba
[not found] ` <e5bfff550712171114i40a59b11md87038a3fc13d29c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 21:40 ` Abdelrazak Younes [this message]
2007-12-17 19:05 ` Marco Costalba
2007-12-17 19:13 ` Johannes Schindelin
[not found] ` <Pine.LNX.4.64.0712171911070.9446-OGWIkrnhIhzN0uC3ymp8PA@public.gmane.org>
2007-12-17 19:17 ` Marco Costalba
2007-12-17 21:22 ` Abdelrazak Younes
[not found] ` <e5bfff550712171105k62b90853w1c5eed64bd11fb23-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-17 21:20 ` Abdelrazak Younes
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=4766ECCE.8010404@free.fr \
--to=younes.a-ganu6spqydw@public.gmane.org \
--cc=Johannes.Schindelin-Mmb7MZpHnFY@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mcostalba-Re5JQEeQqe8AvxtiuMwx3w@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).