git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Windows binaries for qgit 2.0
Date: Sat, 15 Dec 2007 16:02:18 +0100	[thread overview]
Message-ID: <e5bfff550712150702p2675da8axed1f3db6273f619@mail.gmail.com> (raw)

Due to a feature request on sourceforge qgit account:

http://sourceforge.net/tracker/index.php?func=detail&aid=1759403&group_id=139897&atid=744830

I have cooked and uploaded a qgit.exe file with Qt4.3.3 statically
linked in so to let Windows users that just want to give a shot to
qgit the possibility to try it easily.

Normally I use debug shared Qt libraries for development, so after
some effort I finally managed to build the static ones and finally to
build qgit.exe

Problem is that _this_ qgit.exe shows strange misbehaviour like 20X
slower then the one I normally build for development,  there is also
some strange artifacts with file history graph.

I have a clue that is due to static Qt + mingw 3.4 problems, I have
read something on it somewhere, but I would like to ask if someone has
experienced the same problems when running qgit2.0 under Windows.

BTW if someone is interested, in the sourceforge thread above there is
the link to download this zipped file, testing is very easy and quick,
just extract files where git.exe is and start qgit.exe...

Thanks for any help
Marco

             reply	other threads:[~2007-12-15 15:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15 15:02 Marco Costalba [this message]
2007-12-16  7:26 ` Windows binaries for qgit 2.0 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
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=e5bfff550712150702p2675da8axed1f3db6273f619@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --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).