aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorXavier Claessens <xavier.claessens@collabora.com>2018-10-05 12:07:46 -0400
committerXavier Claessens <xavier.claessens@collabora.com>2018-10-17 21:56:49 -0400
commitd6fba7f01ce3effebd18d75ebe3102774353cee0 (patch)
treec15a612132f82350a21fc701a436e1a62ee5d523 /docs/markdown
parenta3db9f6ae3592f863b95c1c32b56ff322812694f (diff)
downloadmeson-d6fba7f01ce3effebd18d75ebe3102774353cee0.zip
meson-d6fba7f01ce3effebd18d75ebe3102774353cee0.tar.gz
meson-d6fba7f01ce3effebd18d75ebe3102774353cee0.tar.bz2
wrap: Allow source and patch to be local files
It is sometimes important to be able to build projects offline, in that case subproject tarballs and patches could be shipped directly within the project's repository.
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/Wrap-dependency-system-manual.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/markdown/Wrap-dependency-system-manual.md b/docs/markdown/Wrap-dependency-system-manual.md
index 2e977b2..7da4be5 100644
--- a/docs/markdown/Wrap-dependency-system-manual.md
+++ b/docs/markdown/Wrap-dependency-system-manual.md
@@ -45,6 +45,11 @@ If you then use this subproject in your build, Meson will
automatically download and extract it during build. This makes
subproject embedding extremely easy.
+Since *0.49.0* if `source_filename` is found in project's
+`subprojects/packagecache` directory, it will be used instead of downloading the
+source, even if `wrap-mode` option is set to `nodownload`. The file's hash will
+be checked.
+
Unfortunately most software projects in the world do not build with
Meson. Because of this Meson allows you to specify a patch URL. This
works in much the same way as Debian's distro patches. That is, they
@@ -76,6 +81,11 @@ thousands of lines of code. Once you have a working build definition,
just zip up the Meson build files (and others you have changed) and
put them somewhere where you can download them.
+Since *0.49.0* if `patch_filename` is found in project's
+`subprojects/packagecache` directory, it will be used instead of downloading the
+patch, even if `wrap-mode` option is set to `nodownload`. The file's hash will
+be checked.
+
## Branching subprojects directly from git
The above mentioned scheme assumes that your subproject is working off