X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;ds=inline;f=docs%2F0_Getting_Started%2F6_%20Developing_an_Application%20%2F7_Deploy_the_Application_to_the_Board.md;fp=docs%2F0_Getting_Started%2F6_%20Developing_an_Application%20%2F7_Deploy_the_Application_to_the_Board.md;h=ee9d6f8bbe833e8162ef83a2137f1e4668d15414;hb=4aad369c9728061c97b3de792286e743ee884b09;hp=0000000000000000000000000000000000000000;hpb=619a7e48085be1538c3b01eb93dcb9dc95bf0436;p=AGL%2Fdocumentation.git

diff --git a/docs/0_Getting_Started/6_ Developing_an_Application /7_Deploy_the_Application_to_the_Board.md b/docs/0_Getting_Started/6_ Developing_an_Application /7_Deploy_the_Application_to_the_Board.md
new file mode 100644
index 0000000..ee9d6f8
--- /dev/null
+++ b/docs/0_Getting_Started/6_ Developing_an_Application /7_Deploy_the_Application_to_the_Board.md	
@@ -0,0 +1,58 @@
+---
+edit_link: ''
+title: Deploy the Application to the Board
+origin_url: >-
+  https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/getting-started/app-workflow-deploy-app.md
+---
+
+<!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/getting_started/master/image-development-workflow-getting-started-book.yml -->
+
+# Deploy the Application to the Board #
+
+
+Many options exist for controlling your target and copying your compiled application to the target.
+Details are target-specific and cannot be explained in detail here.
+
+Suffice it to say that if you compile your application on your build host and you have
+an image running on your target hardware, you must employ some method to copy the application
+to the target.
+Several general methods exist:
+
+  * Write the application to a storage device that both the build host and
+    the target hardware support.
+    This could be an SD card or a flash drive.
+    Be sure to format the drive as FAT32 to eliminate file ownership and permission issues.
+
+  * Remotely mount the target's file system on the build host with the Network File System
+    (NFS) or Samba.
+
+  * Commit compiled code from the build host to a shared repository and update the
+    target from that repository.
+
+  * Use remote commands from a host over a network, such as `scp` (i.e. secure copy).
+
+  * You can set up your build environment to leverage a procedure's
+    [application template](../../../devguides/reference/cmakeafbtemplates/dev_guide/using-cmake.html)
+    (app-template).
+    An app-template is an application framework that contains
+    [CMake](https://cmake.org/) macros that abstract deploying the application.
+    For example, with a proper build environment, you can run the following
+    to deploy your application:
+
+    ```
+    $ make widget-target-install
+    ```
+
+    **NOTE:**
+    The previous command uses `scp` to copy and install the widget to a pre-defined target board.
+
+Once you have the application copied to the target, it must provide a way to
+initiate operating system commands.
+To initiate operating system commands, you can do one of the following:
+
+  * Connect a keyboard and display directly to the target.
+
+  * Use ``ssh`` from a network-connected host to run commands on the target remotely.
+
+  * Use a network for communication between the build host and the target.
+    This method works nicely when the build host and the target hardware are geographically apart.