From: Marco Costalba <mcostalba@gmail.com>
To: git mailing list <git@vger.kernel.org>
Cc: Pavel Roskin <proski@gnu.org>, Junio C Hamano <junkio@cox.net>
Subject: [PATCH] qgit: add some installation instruction
Date: Sat, 04 Feb 2006 15:32:19 +0100 [thread overview]
Message-ID: <43E4BAF3.3040307@gmail.com> (raw)
With this I would start to post possible patches for list review.
I am planning to post only a very limited number of patches that could be interesting or
that modify someone else work (like in this case, the new Pavel build system).
Is not my intention to add noise to the list, so I will try to keep the patches to the minimum.
In any case, please, Junio, feel free to express any concern about this and I will stop as soon
as started!
Thanks
Marco
-- >8 --
Document how to strip debug information and better explaing when to reconfigure
the build environment.
Signed-off-by: Marco Costalba <mcostalba@gmail.com>
---
diff --git a/README b/README
index 0869c0c..f32dce4 100644
--- a/README
+++ b/README
@@ -23,10 +23,11 @@ which is used to locate Qt. Version 0.15
also work.
To compile qgit, unpack the tar file (you probably have done it
-already), run "./configure", "make" and "make install". You may need to
-get root permissions for the later. You can run "configure" with full
-path from another empty directory if you want qgit to be compiled in a
-separate directory.
+already), run "./configure", "make" and "make install" or "make install-strip"
+to have debug information removed and install a much smaller bin.
+You may need to get root permissions for the later. You can run "configure"
+with full path from another empty directory if you want qgit to be compiled
+in a separate directory.
If there is another qgit executable in PATH, "make install" will
overwrite it. Otherwise, qgit will be installed in /usr/local/bin. You
@@ -41,6 +42,8 @@ Automake, preferably the latest versions
Only in case you clone the public qgit repository you may need to run
"autoreconf -i" the first time to create the ./configure file. Do not need
to run it on a released tarball.
+You may need to run "autoreconf -i" also when pulling revisions that modify
+some build system file, as "configure.ac".
Command line arguments
---
reply other threads:[~2006-02-04 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43E4BAF3.3040307@gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.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).