Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
It would be nice to have binaries now that qgit uses Qt 4 and works under Windows. An maybe even an installer using Inno Setup (http://www.jrsoftware.org/isinfo.php).
Logged In: YES
Yes. It would be nice. There is already something cooking. I think for qgit2.0 final release we will have a nice Windows installer.
Logged In: YES
Any update on this? I would be willing to contribute the installer (I also did the Inno Setup installer for the "Git on MSys" project hosted at <http://code.google.com/p/msysgit/>) if you would provide Windows binaries (but please do *not* use Cygwin to build them) as a ZIP package on the download page :-)
Maybe it would even make sense to bundle QGit with the "Git on MSys" installer, depending on it's size.
Another idea would be to have an installer separate from "Git on MSys" which comes with "Qt tools for Git" and would contain QGit (as a replacement for gitk) and ugit (see <http://repo.or.cz/w/ugit.git/>) as a replacement for git-gui.
Logged In: NO
I never use Cygwin for qgit under Windows. For compile you just need Qt4 libraries (MinGw is already bundled with Qt4).
Bundle QGit with the "Git on MSys" installer would be very very nice. Size of qgit binary under Linux is around 980K so it's small.
Probably are the Qt4 libraries that need some space.
Anyhow I can provide the qgit.exe file, but I strongly suggest to download the sources and compile your self (should be very easy following the README) so that you can tweak compilation flags to get the best size compromise between qgit.exe and Qt4 ddl.
Please tell me if you need any help.
I think especially for Windows users who "just want to quickly try out QGit" (e.g. to compare it to gitk) it would be nice to have zipped QGit binary ready for download anyways. It should probably be linked statically against Qt to keep the distribution size down (otherwise you would have to include the Qt libraries into the download to make it run out of the box). If you already have an environment with static Qt libraries set up, it would be cool if you could build the binary.
For inclusion into some installer, be it "Git on MSys" or my suggested "Qt tools for Git" installer, we would probably rather link QGit dynamically against Qt. However, this would require the (big) Qt DLLs to be bundled. My feeling is that the "Git on MSys" people would not be happy with this. Thus my idea of the "Qt tools for Git" installer.
Ok. I will post a static linked qgit file...
Need some tme to cook because I have installed the shared Qt libraries.
Here we are, this is a zipped file with qgit 2.0 compiled with Qt linked statically for windows:
Please, be informed that I have found a lot of problems with this version, it seems statically
compiled release Qt4.3.3. have problems.
Normally I use Qt shared debug dll and had not experienced this kind of strange misbheaviours:file history sometimes does not work, loading a repo is 20X slower then normal, etc..
I'll post a message also on git mailing list in case someone had same problems with the statically
linked Qt libraries.
Anyhow the zipped file should be enough for you to try to package...
Let me know how it goes.
I was trying to build a version using VS2005 to see if it has the same problems. I checkout out the sources from CVS, but they seem to be from version 1.5.6. Is version 2.0 not in CVS?
Right, CVS is for stable 1.5 series.
You can download qgit2.0 tarball on sourceforge or,better, the current development version from git public repo:
I say this latter one is better because James McKaskill has contributed VS2008 project and solution files. So probably is easier for you (and is also a better version with bug fixed and probably more stable then released one).
Which is the branch I'm supposed to checkout, master or HEAD? If needed, could I push changes to you (as you don't seem to have a mob branch or the like)?
Master branch (points to revision: "Open file names cache in unbuffered mode")
Please send your patches to me (email@example.com) , I will push upstream for you.