From: Abdelrazak Younes <younes.a@free.fr>
To: git@vger.kernel.org
Subject: Re: Windows binaries for qgit 2.0
Date: Sun, 16 Dec 2007 09:52:27 +0100 [thread overview]
Message-ID: <fk2p0f$961$1@ger.gmane.org> (raw)
In-Reply-To: <e5bfff550712152355o7c8ef2f3j95f239697f77ccef@mail.gmail.com>
Marco Costalba wrote:
> On Dec 16, 2007 8:26 AM, Abdelrazak Younes <younes.a@free.fr> wrote:
>> Sorry for the intrusion in this list but you don't need to compile Qt
>> statically IMO. Just bundle the Qt dlls that you needs (most probably
>> QtCore and QtGui) with you executable and be done with it.
>>
>
> Yes. That's another option, I will try that to see if things get better.
>
>> If you are using debug dlls, those are known to be slower because of
>
> Actually I use debug dll for normal development and never experienced slowness.
> I switched to "release" library to create the qgit package and _now_ I
> have the thing much slower and also misbehaving. So for me are the
> release library that have problems, not the debug ones.
Hum, I can't imagine this is the reason, it might be for another reason,
most certainly the static compiling.
>
>> In any case, if you want to gain
>> speed, you should compile with MSVC (MSVC2005Express is free as in beer).
>>
>
> Yes, I was thinking about this, but Qt don't officially supports MSVC
> for the Qt4 GPL libraries,
Well, for the LyX project we used to use and distribute the patched
version of Qt in order to compile it with MSVC. Now, since Qt4.3.2 the
MSVC compilation support is enabled in the official release so you don't
even have to patch it anymore. I can send you precompiled dll if you
want. Or you can use the one bundled in the last lyx installer
(www.lyx.org).
> so that's the reason I was stick to mingw
> (although now it comes more and more clear to me that the shipped
> version has problems with release compiled libraries)
The first reason why we went away from mingw was because it was way too
slow to compile Qt and LyX. With MSVC the binaries are much faster.
Abdel.
next prev parent reply other threads:[~2007-12-16 8:53 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 [this message]
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
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='fk2p0f$961$1@ger.gmane.org' \
--to=younes.a@free.fr \
--cc=git@vger.kernel.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).