aboutsummaryrefslogtreecommitdiff
path: root/doc/contributing.texi
diff options
context:
space:
mode:
authorRovanion Luckey <rovanion.luckey@gmail.com>2020-12-15 12:33:12 +0100
committerJakub Kądziołka <kuba@kadziolka.net>2021-01-03 23:35:29 +0100
commitad911c832178216b0121c6ecb8349d1a9d68526f (patch)
tree738bf4729299c51d5af7963033cc745e359c8993 /doc/contributing.texi
parent1670de3910c14d5fa9d2c6cd07aa31088f94b7fe (diff)
downloadguix-ad911c832178216b0121c6ecb8349d1a9d68526f.tar
guix-ad911c832178216b0121c6ecb8349d1a9d68526f.tar.gz
doc: Running Guix Before It Is Installed: mention ./bootstrap
* doc/contributing.texi (Running Guix Before It Is Installed): Instruct user to run ./bootstrap before ./configure. Signed-off-by: Jakub Kądziołka <kuba@kadziolka.net>
Diffstat (limited to 'doc/contributing.texi')
-rw-r--r--doc/contributing.texi17
1 files changed, 9 insertions, 8 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 4195cb4105..d0ab08336a 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -166,14 +166,15 @@ actually installing them. So that you can distinguish between your
``end-user'' hat and your ``motley'' costume.
To that end, all the command-line tools can be used even if you have not
-run @code{make install}. To do that, you first need to have an environment
-with all the dependencies available (@pxref{Building from Git}), and then
-simply prefix each command with
-@command{./pre-inst-env} (the @file{pre-inst-env} script lives in the
-top build tree of Guix; it is generated by @command{./configure}).
-As an example, here is how you would build the @code{hello} package as
-defined in your working tree (this assumes @command{guix-daemon} is
-already running on your system; it's OK if it's a different version):
+run @code{make install}. To do that, you first need to have an
+environment with all the dependencies available (@pxref{Building from
+Git}), and then simply prefix each command with @command{./pre-inst-env}
+(the @file{pre-inst-env} script lives in the top build tree of Guix; it
+is generated by running @command{./bootstrap} followed by
+@command{./configure}). As an example, here is how you would build the
+@code{hello} package as defined in your working tree (this assumes
+@command{guix-daemon} is already running on your system; it's OK if it's
+a different version):
@example
$ ./pre-inst-env guix build hello