Fix broken links in documentation

foonathan · foonathan · commit 92a5bfc53b97 · 2025-05-29T11:02:22.000+02:00
Fixes #191. See doxygen/doxygen#10721.
diff --git a/doc/adapters_storage.md b/doc/adapters_storage.md
@@ -1,4 +1,4 @@
-# Allocator adapters and storage classes
+# Allocator adapters and storage classes {#md_doc_adapters_storage}
 
 In addition to the various allocator classes, it also provides a couple of adapters and storage classes for [RawAllocator] instances.
 
diff --git a/doc/concepts.md b/doc/concepts.md
@@ -1,4 +1,4 @@
-# Concepts and overall requirements
+# Concepts and overall requirements {#md_doc_concepts}
 
 ## Node
 <a name="concept_node"></a>
diff --git a/doc/debug_error.md b/doc/debug_error.md
@@ -1,4 +1,4 @@
-# Debugging options and error handling
+# Debugging options and error handling {#md_doc_debug_error}
 
 ## Error handling
 
diff --git a/doc/external_usage.md b/doc/external_usage.md
@@ -1,4 +1,4 @@
-# Using RawAllocators in STL containers, smart pointers, etc.
+# Using RawAllocators in STL containers, smart pointers, etc. {#md_doc_external_usage}
 
 ## 1. Using Containers with RawAllocators
 
diff --git a/doc/installation.md b/doc/installation.md
@@ -1,4 +1,4 @@
-# Installation
+# Installation {#md_doc_installation}
 
 This library can either be used [CMake]'s `add_subdirectory()` command or installed globally.
 
diff --git a/doc/internal_usage.md b/doc/internal_usage.md
@@ -1,4 +1,4 @@
-# Writing classes using a RawAllocator
+# Writing classes using a RawAllocator {#md_doc_internal_usage}
 
 Compared to the requirements an `AllocatorAwareContainer` has to fulfill,
 it is very easy to use a `RawAllocator` in a container.
diff --git a/doc/options.md b/doc/options.md
@@ -1,4 +1,4 @@
-# CMake options for configuring the library
+# CMake options for configuring the library {#md_doc_options}
 
 When installing the library, each build type (`-DCMAKE_BUILD_TYPE=XXX`) allows a separate configuration.
 The configuration doesn't affect your targets, you can link to any configuration (your compiler might complain though, if you link your debug target to a library compiled in release mode or vice-versa).
diff --git a/doc/tutorial.md b/doc/tutorial.md
@@ -1,4 +1,4 @@
-# Tutorial
+# Tutorial {#md_doc_tutorial}
 
 ## Installation and Setup
 
@@ -15,4 +15,4 @@
 
 * [Writing own RawAllocator classes](md_doc_writing_allocators.html)
 * [Debugging options and error handling](md_doc_debug_error.html)
-* [Concepts](md_doc_concepts.html)
+* [Concepts](md_doc_concepts.html)
diff --git a/doc/writing_allocators.md b/doc/writing_allocators.md
@@ -1,4 +1,4 @@
-# Writing own RawAllocator classes
+# Writing own RawAllocator classes {#md_doc_writing_allocators}
 
 There are, in general, three different ways and one special case to write a [RawAllocator] class.
 See the link for the exact requirements and behavior for each function.

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Allocator adapters and storage classes`
	`1`	`+# Allocator adapters and storage classes {#md_doc_adapters_storage}`
`2`	`2`
`3`	`3`	`In addition to the various allocator classes, it also provides a couple of adapters and storage classes for [RawAllocator] instances.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Concepts and overall requirements`
	`1`	`+# Concepts and overall requirements {#md_doc_concepts}`
`2`	`2`
`3`	`3`	`## Node`
`4`	`4`	`<a name="concept_node"></a>`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Debugging options and error handling`
	`1`	`+# Debugging options and error handling {#md_doc_debug_error}`
`2`	`2`
`3`	`3`	`## Error handling`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Using RawAllocators in STL containers, smart pointers, etc.`
	`1`	`+# Using RawAllocators in STL containers, smart pointers, etc. {#md_doc_external_usage}`
`2`	`2`
`3`	`3`	`## 1. Using Containers with RawAllocators`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Installation`
	`1`	`+# Installation {#md_doc_installation}`
`2`	`2`
`3`	`3`	This library can either be used [CMake]'s `add_subdirectory()` command or installed globally.
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Writing classes using a RawAllocator`
	`1`	`+# Writing classes using a RawAllocator {#md_doc_internal_usage}`
`2`	`2`
`3`	`3`	Compared to the requirements an `AllocatorAwareContainer` has to fulfill,
`4`	`4`	it is very easy to use a `RawAllocator` in a container.
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# CMake options for configuring the library`
	`1`	`+# CMake options for configuring the library {#md_doc_options}`
`2`	`2`
`3`	`3`	When installing the library, each build type (`-DCMAKE_BUILD_TYPE=XXX`) allows a separate configuration.
`4`	`4`	`The configuration doesn't affect your targets, you can link to any configuration (your compiler might complain though, if you link your debug target to a library compiled in release mode or vice-versa).`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Writing own RawAllocator classes`
	`1`	`+# Writing own RawAllocator classes {#md_doc_writing_allocators}`
`2`	`2`
`3`	`3`	`There are, in general, three different ways and one special case to write a [RawAllocator] class.`
`4`	`4`	`See the link for the exact requirements and behavior for each function.`