summaryrefslogtreecommitdiffstats
path: root/docs/04_Developer_Guides
diff options
context:
space:
mode:
Diffstat (limited to 'docs/04_Developer_Guides')
-rw-r--r--docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md2
-rw-r--r--docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md3
-rw-r--r--docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md7
-rw-r--r--docs/04_Developer_Guides/03_Creating_a_New_Application.md2
4 files changed, 6 insertions, 8 deletions
diff --git a/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md b/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
index 232f41e..2786bf6 100644
--- a/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
+++ b/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
@@ -73,7 +73,7 @@ any valid string, it is highly recommended to use the "reverse DNS" convention i
to avoid potential name collisions and ease D-Bus integration.
The application ID is set in the desktop entry file itself for
-[graphical applications](../3_Creating_a_New_Application/#graphical-applications):
+[graphical applications](/04_Developer_Guides/03_Creating_a_New_Application/#graphical-applications):
it is the value of the `StartupWMClass` field, which must be identical to the `app-id`
advertised through the Wayland XDG toplevel protocol. In case this field is missing
(as is usually the case for non-graphical application), the application ID will be the
diff --git a/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md b/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
index 1ac45a6..28ba02a 100644
--- a/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
+++ b/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
@@ -10,7 +10,7 @@ You use this layer as the minimal core on which to build AGL profiles.
**NOTE:** The `meta-agl` layer does not include a reference UI.
The reference UI is included as part of the
- [`meta-agl-demo`](3_meta-agl-demo.md) layer.
+ [`meta-agl-demo`](03_meta_agl_demo.md) layer.
Furthermore, `meta-agl` does not include additional components, such
as security, which are part of the
`meta-agl-extra` layer.
@@ -121,4 +121,3 @@ design:
* packagegroup-agl-test.bb
Additional tools used in QA tests (for agl-image*-qa).
-
diff --git a/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md b/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
index c560989..dbfe374 100644
--- a/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
+++ b/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
@@ -58,8 +58,7 @@ The `meta-agl-demo` layer has the following base dependencies:
### Hardware Dependencies
Aside from the previously listed base dependencies, if you are using a
-[supported Renesas board](../../0_Getting_Started/2_Building_AGL_Image/5_3_RCar_Gen_3.md)
-supported Renesas board, these dependencies exist:
+[supported Renesas board](/01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards.md), these dependencies exist:
- AGL's `meta-renesas` Layer:
@@ -67,7 +66,7 @@ supported Renesas board, these dependencies exist:
### Feature Dependencies
-The `meta-agl-demo` layer has the following AGL [feature](../../0_Getting_Started/2_Building_AGL_Image/3_Initializing_Your_Build_Environment.md#agl-features)
+The `meta-agl-demo` layer has the following AGL [feature](/01_Getting_Started/02_Building_AGL_Image/04_Initializing_Your_Build_Environment/#agl-features)
dependencies:
- Yocto Project `meta-security` Layer:
@@ -156,4 +155,4 @@ consist of the following:
Because the `packagegroup-agl-demo-qt-examples` is not mandatory for the AGL
Application Framework and the AGL DEMO, the packagegroup is added to the layer's
- `local.conf` file only when needed. \ No newline at end of file
+ `local.conf` file only when needed.
diff --git a/docs/04_Developer_Guides/03_Creating_a_New_Application.md b/docs/04_Developer_Guides/03_Creating_a_New_Application.md
index 3fb7682..014069d 100644
--- a/docs/04_Developer_Guides/03_Creating_a_New_Application.md
+++ b/docs/04_Developer_Guides/03_Creating_a_New_Application.md
@@ -60,7 +60,7 @@ refer to the [graphical applications](#graphical-applications) section for more
# D-Bus activation
-Similarly to [services](../2_Creating_a_New_Service/#d-bus-activation), applications can
+Similarly to [services](../02_Creating_a_New_Service/#d-bus-activation), applications can
also be activated through D-Bus.
Such applications must name their `.desktop` file after the D-Bus name they register. In addition,