Split out documentation into subfolders.

[platform/upstream/gstreamer.git] / markdown / deploying / multiplatform-using-cerbero.md

diff --git a/deploying-multiplatform-using-cerbero.md b/markdown/deploying/multiplatform-using-cerbero.md
similarity index 97%
rename from deploying-multiplatform-using-cerbero.md
rename to markdown/deploying/multiplatform-using-cerbero.md
index 729b2e1..7b1e178 100644 (file)
--- a/deploying-multiplatform-using-cerbero.md
+++ b/markdown/deploying/multiplatform-using-cerbero.md
@@ -12,11 +12,11 @@ add a recipe explaining how to build you application and make it depend
 on the `gstreamer-sdk` project. Then Cerbero can take care of building
 your application and its dependencies and package them all together.
 
-Read [](building-from-source-using-cerbero.md) to learn how
+Read [](installing/building-from-source-using-cerbero.md) to learn how
 to install and use Cerbero.
 
 At this point, after reading the Build from source section in
-[](building-from-source-using-cerbero.md), you should be able to
+[](installing/building-from-source-using-cerbero.md), you should be able to
 build GStreamer from source and are ready to create recipe and package
 files for your application.
 
@@ -115,7 +115,7 @@ class Recipe(recipe.Recipe):
 Cerbero gets the software sources to build from a GIT repository, which
 is specified via the `git_root` configuration variable from the Cerbero
 configuration file (see the "Build from software" section in [Installing
-on Linux](installing-on-linux.md)) and can be overridden by the
+on Linux](installing/on-linux.md)) and can be overridden by the
 `remotes` attribute inside the recipes (if setting the `origin` remote).
 In this case where no “commit” attribute is specified, Cerbero will use
 the commit named “sdk-0.2+git” from the GIT repository when building
@@ -237,7 +237,7 @@ packages\_prefix as the ones in your Cerbero configuration file.
 Finally, build your package by using:
 
 ``` bash
-./cerbero-uninstalled package your-package 
+./cerbero-uninstalled package your-package
 ```
 
 Where `your-package` is the name of the `.package` file that you created