From: "Marco Costalba" <mcostalba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Peter Klavins" <klavins-ooduxAEi7gXtt0EhB6fy4g@public.gmane.org>
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [ANNOUNCE] qgit2.1rc1_win.exe
Date: Thu, 27 Dec 2007 00:23:36 +0100 [thread overview]
Message-ID: <e5bfff550712261523g7aab6e76nd37257e7b21d1653@mail.gmail.com> (raw)
In-Reply-To: <fkugn8$d2s$1@ger.gmane.org>
On Dec 26, 2007 10:22 PM, Peter Klavins <klavins-ooduxAEi7gXtt0EhB6fy4g@public.gmane.org> wrote:
>
> 4. configure (takes significant time, around 10 minutes from
> memory)
configure -fast -no-qt3support -static -release -no-qmake
Takes much less (about one minute)
> 5. nmake (takes over an hour on a Core 2 Duo 2 GHz,
> consumes 2 GByte of disk)
>
2GBytes because default configure is -debug, but giving -release
instead the needed space is much less because debug symbols are not
built.
Also use:
nmake sub-src
30minutes on my Core Duo 1.5Ghz. It just compiles the Qt libraries
under src directory, not Qt tools like designer, assistant and
expecially the Qt examples.
Note: first you need to run nmake to build makefile then, just after
the makefile in main directory is built (few seconds) you can stop it
and run nmake sub-src.
> 16. bin\qgit (to run qgit to browse qgit4's own repository!)
>
msysgit must be in PATH, both Git\cmd and Git\bin. Or you can use the
launch script start_qgit.bat that just adds msysgit to the PATH for
you before to call qgit.exe
> ------------------------------------------------------------------------
> Peter Klavins
>
Thanks Peter,
Just a question. How about using the auto-extract zip I advertise in
this thread? With this both Qt and qgit are already compiled and
should be ready to go.
Marco
next prev parent reply other threads:[~2007-12-26 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 9:13 [ANNOUNCE] qgit2.1rc1_win.exe Marco Costalba
[not found] ` <e5bfff550712240113y4acdaa11y3483705172a5980e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-26 21:22 ` Peter Klavins
2007-12-26 23:23 ` Marco Costalba [this message]
[not found] ` <e5bfff550712261523g7aab6e76nd37257e7b21d1653-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-26 23:37 ` Peter Klavins
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=e5bfff550712261523g7aab6e76nd37257e7b21d1653@mail.gmail.com \
--to=mcostalba-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=klavins-ooduxAEi7gXtt0EhB6fy4g@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).