From 603b1ac287d73c5d2dfa3fdcb6402a082ed2c236 Mon Sep 17 00:00:00 2001 From: Anton Leontiev Date: Sat, 19 Oct 2019 12:40:52 +0300 Subject: [PATCH] docs: Fix some incorrect links [skip ci] --- docs/markdown/Builtin-options.md | 2 +- docs/markdown/Contributing.md | 2 +- docs/markdown/D.md | 4 ++-- docs/markdown/Gnome-module.md | 5 +++-- docs/markdown/Native-environments.md | 2 +- docs/markdown/Python-3-module.md | 2 +- docs/markdown/Reference-manual.md | 2 +- docs/markdown/Release-notes-for-0.47.0.md | 6 +++--- docs/markdown/Release-notes-for-0.48.0.md | 2 +- docs/markdown/Subprojects.md | 2 +- 10 files changed, 15 insertions(+), 14 deletions(-) diff --git a/docs/markdown/Builtin-options.md b/docs/markdown/Builtin-options.md index cb8c53cc9087..3219af85f159 100644 --- a/docs/markdown/Builtin-options.md +++ b/docs/markdown/Builtin-options.md @@ -121,7 +121,7 @@ The value of `b_sanitize` can be one of: `none`, `address`, `thread`, `-Wl,-bitcode_bundle` while linking. These options are incompatible with `b_asneeded`, so that option will be silently disabled. -[Shared modules](#Reference-manual.md#shared_module) will not have bitcode +[Shared modules](Reference-manual.md#shared_module) will not have bitcode embedded because `-Wl,-bitcode_bundle` is incompatible with both `-bundle` and `-Wl,-undefined,dynamic_lookup` which are necessary for shared modules to work. diff --git a/docs/markdown/Contributing.md b/docs/markdown/Contributing.md index 143cdcb62092..a7ddd6c4ea3f 100644 --- a/docs/markdown/Contributing.md +++ b/docs/markdown/Contributing.md @@ -36,7 +36,7 @@ Every new feature requires some extra steps, namely: - Must include a project test under `test cases/`, or if that's not possible or if the test requires a special environment, it must go into `run_unittests.py`. - - Must be registered with the [FeatureChecks framework](Release-notes-for-0.47.0.md#Feature_detection_based_on_meson_version_in_project) + - Must be registered with the [FeatureChecks framework](Release-notes-for-0.47.0.md#feature-detection-based-on-meson_version-in-project) that will warn the user if they try to use a new feature while targetting an older meson version. - Needs a release note snippet inside `docs/markdown/snippets/` with diff --git a/docs/markdown/D.md b/docs/markdown/D.md index 2b0eaac5afc0..ed8986b1fb8e 100644 --- a/docs/markdown/D.md +++ b/docs/markdown/D.md @@ -113,5 +113,5 @@ compilers will lead to problems. DUB is a fully integrated build system for D, but it is also a way to provide dependencies. Adding dependencies from the [D package registry](https://code.dlang.org/) is pretty straight forward. You can find how to do this in -[Dependencies](Dependencies.md#Dub). You can also automatically -generate a `dub.json` file as explained in [Dlang](Dlang-module.md#generatedubfile). +[Dependencies](Dependencies.md#some-notes-on-dub). You can also automatically +generate a `dub.json` file as explained in [Dlang](Dlang-module.md#generate_dub_file). diff --git a/docs/markdown/Gnome-module.md b/docs/markdown/Gnome-module.md index 9d8029eaaeeb..a9c45317185c 100644 --- a/docs/markdown/Gnome-module.md +++ b/docs/markdown/Gnome-module.md @@ -225,8 +225,9 @@ useful when running the application locally for example during tests. * `build_by_default`: causes, when set to true, to have this target be built by default, that is, when invoking plain `ninja`, the default value is true for all built target types -* `depend_files`: files ([`string`](#string-object), - [`files()`](#files), or [`configure_file()`](#configure_file)) of +* `depend_files`: files ([`string`](Reference-manual.md#string-object), + [`files()`](Reference-manual.md#files), or + [`configure_file()`](Reference-manual.md#configure_file)) of schema source XML files that should trigger a re-compile if changed. ### gnome.gdbus_codegen() diff --git a/docs/markdown/Native-environments.md b/docs/markdown/Native-environments.md index f0d41ebe4d49..9adddc7ab0e9 100644 --- a/docs/markdown/Native-environments.md +++ b/docs/markdown/Native-environments.md @@ -23,7 +23,7 @@ persistent environment: ## Changing native file settings All of the rules about cross files and changed settings apply to native files -as well, see [here](Cross-compilation.md#Changing-cross-file-settings) +as well, see [here](Cross-compilation.md#changing-cross-file-settings) ## Defining the environment diff --git a/docs/markdown/Python-3-module.md b/docs/markdown/Python-3-module.md index 50ec4e41454d..f32cdc98ba8e 100644 --- a/docs/markdown/Python-3-module.md +++ b/docs/markdown/Python-3-module.md @@ -25,7 +25,7 @@ arguments are the same as for `extension_module` does not add any dependencies to the library so user may need to add `dependencies : dependency('python3')`, see -[Python3 dependency](Dependencies.md#Python3). +[Python3 dependency](Dependencies.md#python3). *Added 0.38.0* diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md index d492096307f4..832ceda5273e 100644 --- a/docs/markdown/Reference-manual.md +++ b/docs/markdown/Reference-manual.md @@ -419,7 +419,7 @@ keyword arguments. Finds an external dependency (usually a library installed on your system) with the given name with `pkg-config` and [with -CMake](Dependencies.md#CMake) if `pkg-config` fails. Additionally, +CMake](Dependencies.md#cmake) if `pkg-config` fails. Additionally, frameworks (OSX only) and [library-specific fallback detection logic](Dependencies.md#dependencies-with-custom-lookup-functionality) are also supported. This function supports the following keyword diff --git a/docs/markdown/Release-notes-for-0.47.0.md b/docs/markdown/Release-notes-for-0.47.0.md index a427a7214372..675942be49d4 100644 --- a/docs/markdown/Release-notes-for-0.47.0.md +++ b/docs/markdown/Release-notes-for-0.47.0.md @@ -50,7 +50,7 @@ Note: When building with clang on macOS, you can now build your static and shared binaries with embedded bitcode by enabling the `b_bitcode` [base -option](Builtin-options.md#Base_options) by passing `-Db_bitcode=true` to +option](Builtin-options.md#base-options) by passing `-Db_bitcode=true` to Meson. This is better than passing the options manually in the environment since Meson @@ -78,7 +78,7 @@ used whenever possible. ## New action `copy:` for `configure_file()` In addition to the existing actions `configuration:` and `command:`, -[`configure_file()`](#Reference-manual.md#configure_file) now accepts a keyword +[`configure_file()`](Reference-manual.md#configure_file) now accepts a keyword argument `copy:` which specifies a new action to copy the file specified with the `input:` keyword argument to a file in the build directory with the name specified with the `output:` keyword argument. @@ -88,7 +88,7 @@ do one action at a time. ## New keyword argument `encoding:` for `configure_file()` -Add a new keyword to [`configure_file()`](#Reference-manual.md#configure_file) +Add a new keyword to [`configure_file()`](Reference-manual.md#configure_file) that allows the developer to specify the input and output file encoding. The default value is the same as before: UTF-8. diff --git a/docs/markdown/Release-notes-for-0.48.0.md b/docs/markdown/Release-notes-for-0.48.0.md index a89f5c929759..2cb02684ea35 100644 --- a/docs/markdown/Release-notes-for-0.48.0.md +++ b/docs/markdown/Release-notes-for-0.48.0.md @@ -29,7 +29,7 @@ manually changed with the new base option `b_vscrt`. ## Meson warns if two calls to `configure_file()` write to the same file -If two calls to [`configure_file()`](#Reference-manual.md#configure_file) +If two calls to [`configure_file()`](Reference-manual.md#configure_file) write to the same file Meson will print a `WARNING:` message during configuration. For example: ```meson diff --git a/docs/markdown/Subprojects.md b/docs/markdown/Subprojects.md index fc845ff06661..91b1843751f2 100644 --- a/docs/markdown/Subprojects.md +++ b/docs/markdown/Subprojects.md @@ -20,7 +20,7 @@ It should be noted that this is only guaranteed to work for subprojects that are built with Meson. The reason is the simple fact that there is no possible way to do this reliably with mixed build systems. Because of this, only meson subprojects are described here. -[CMake based subprojects](CMake-module.md#CMake-subprojects) are also +[CMake based subprojects](CMake-module.md#cmake-subprojects) are also supported but not guaranteed to work. ## A subproject example