summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRichard Maw <richard.maw@codethink.co.uk>2013-06-27 13:35:39 +0100
committerRichard Maw <richard.maw@codethink.co.uk>2013-06-27 14:25:27 +0100
commit0b9b85619fefe0d2718f43afe6a588fa7e1b483a (patch)
tree2e68cd22b3bbbda71b48c963b4d9d71946919283 /README
parentfac0f4bddf639c2a8e5af4c3ab7b0dee5933d56a (diff)
downloadmorph-0b9b85619fefe0d2718f43afe6a588fa7e1b483a.tar.gz
Update build environment description
Diffstat (limited to 'README')
-rw-r--r--README7
1 files changed, 6 insertions, 1 deletions
diff --git a/README b/README
index 2fe4eaed..8c3054a3 100644
--- a/README
+++ b/README
@@ -226,7 +226,12 @@ When `morph` runs build commands, it clears the environment of all
variables and creates new ones. This is so that the build will run
more consistently across machines and developers.
-See the `morphlib/builder.py` file, method `setup_env` for details.
+See the `morphlib/buildenvironment.py` file for details on what
+environment variables are set.
+
+Morph also constructs a staging area for every build, composed of its
+build-dependencies, so everything that is used for a build is traceable
+and reproducible.
Hacking morph