From 9d097a780c0ffe2c9dbe146046d5b68123c47708 Mon Sep 17 00:00:00 2001
From: Waldemar Brodkorb <wbx@openadk.org>
Date: Sun, 16 Mar 2014 19:51:41 +0100
Subject: add OpenADK manual.

---
 docs/using-openadk-toolchain.txt | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 docs/using-openadk-toolchain.txt

(limited to 'docs/using-openadk-toolchain.txt')

diff --git a/docs/using-openadk-toolchain.txt b/docs/using-openadk-toolchain.txt
new file mode 100644
index 000000000..1b294d4da
--- /dev/null
+++ b/docs/using-openadk-toolchain.txt
@@ -0,0 +1,19 @@
+// -*- mode:doc; -*-
+// vim: set syntax=asciidoc:
+
+Using the generated toolchain outside OpenADK
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You may want to compile, for your target, your own programs or other software
+that are not packaged in OpenADK. In order to do this you can use the toolchain
+that was generated by OpenADK.
+
+The toolchain generated by OpenADK is located by default in
++host_<gnu_host_name>/+. The simplest way to use it is to add
++host_<gnu_host_name>/bin/+ to your PATH environment variable and then to use
++<arch>-<vendor>-linux-<libcsuffix>-gcc+,
++<arch>-<vendor>-linux-<libcsuffix>-objdump+, etc.
+
+It is possible to relocate the toolchain, you just need to put
++target_<arch>_<libc>_<abi>+ into the same directory as
++host_<gnu_host_name>/+.
-- 
cgit v1.2.3