aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXavier Claessens <xavier.claessens@collabora.com>2023-03-28 13:54:51 -0400
committerJussi Pakkanen <jpakkane@gmail.com>2023-03-28 21:46:32 +0300
commit748a1db1f8ea173b6f5841ce17876452424333d4 (patch)
tree8c61a1aaf2d4cbe2608572ba17cf51ef9596bb55
parent697b42f022e6c514798b64e70894c72c8ad2b1a8 (diff)
downloadmeson-748a1db1f8ea173b6f5841ce17876452424333d4.zip
meson-748a1db1f8ea173b6f5841ce17876452424333d4.tar.gz
meson-748a1db1f8ea173b6f5841ce17876452424333d4.tar.bz2
doc: Fix some broken links
-rw-r--r--docs/markdown/Compiler-properties.md2
-rw-r--r--docs/yaml/objects/external_program.yaml4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/markdown/Compiler-properties.md b/docs/markdown/Compiler-properties.md
index adbaa1d..de28d9b 100644
--- a/docs/markdown/Compiler-properties.md
+++ b/docs/markdown/Compiler-properties.md
@@ -3,7 +3,7 @@
Not all compilers and platforms are alike. Therefore Meson provides
the tools to detect properties of the system during configure time. To
get most of this information, you first need to extract the *[compiler
-object](Reference-manual_returned_compiler.html)* from the main
+object](Reference-manual_returned_compiler.md)* from the main
*meson* variable.
```meson
diff --git a/docs/yaml/objects/external_program.yaml b/docs/yaml/objects/external_program.yaml
index f0a5ac0..d175a01 100644
--- a/docs/yaml/objects/external_program.yaml
+++ b/docs/yaml/objects/external_program.yaml
@@ -18,7 +18,7 @@ methods:
**NOTE:** You should not usually need to use this method. Passing the
object itself should work in most contexts where a program can appear,
and allows Meson to setup inter-target dependencies correctly (for
- example in cases where a program might be overridden by a [[build_tgt]]).
+ example in cases where a program might be overridden by a [[@build_tgt]]).
Only use this if you specifically need a string, such as when embedding
a program path into a header file.
@@ -45,7 +45,7 @@ methods:
**NOTE:** You should not usually need to use this method. Passing the
object itself should work in most contexts where a program can appear,
and allows Meson to setup inter-target dependencies correctly (for
- example in cases where a program might be overridden by a [[build_tgt]]).
+ example in cases where a program might be overridden by a [[@build_tgt]]).
Only use this if you specifically need a string, such as when embedding
a program path into a header file.