source: rtems-docs/user/start/index.rst @ d7caf8a

5
Last change on this file since d7caf8a was d7caf8a, checked in by Sebastian Huber <sebastian.huber@…>, on 01/23/19 at 13:33:06

user: Add "Build Your Application"

  • Property mode set to 100644
File size: 3.2 KB
Line 
1.. SPDX-License-Identifier: CC-BY-SA-4.0
2
3.. Copyright (C) 2016 Chris Johns <chrisj@rtems.org>
4
5.. index:: Quick Start
6
7.. _QuickStart:
8
9Quick Start
10***********
11
12Follow the sections of this chapter step by step to get started developing
13applications on top of RTEMS.
14
15.. toctree::
16    :maxdepth: 5
17    :numbered:
18
19    host
20    prefixes
21    sources
22    tools
23    bootstrap
24    bsp-build
25    bsp-test
26    app
27
28The following is a quick start guide that provides a basic set of commands to
29build the RTEMS Tools and Kernel. The quick start guide provides links to the
30detailed sections if any problems are encountered.
31
32The detailed procedure for installing an RTEMS Workspace and installing
33all tools can be found in :ref:`installation`. This includes information
34on installation points, developer versions, and the RTEMS kernel.
35
36The short version of this procedure is as follows
37(:ref:`posix-host-tools-chain`):
38
39#. Create a workspace (:ref:`installation`),
40
41#. Download the RTEMS Source Builder (RSB),
42
43#. Build an RTEMS tool chain for a specific target architecture,
44
45#. Download RTEMS, and then
46
47#. Build RTEMS for a specific Board Support Package (BSP).
48
49Each of these steps is described in a section in this guide.
50
51Creating a Workspace
52====================
53
54Before beginning, the development host computer needs to be set up for
55this quick start procedure to complete successfully. :ref:`host-computer`
56details what is needed for the supported host operating systems. If
57Windows is being used it is recommended following the procedure in
58:ref:`microsoft-windows` first.
59
60There are many ways and locations a suitable environment can be set up. A
61common factor that defines the final location of tools and projects is the
62place you have suitable storage. Another is permissions.  There is no
63need to become root or the administrator and we recommend you avoid
64doing this. You can build and install the tools anywhere on the host's
65file system you, as a standard user, have read and write access too.
66:ref:`Prefixes` and :ref:`ProjectSandboxing` provide detailed examples
67of possible locations and set ups.
68
69Simple Example
70==============
71
72.. code-block:: shell
73
74  $ cd
75  $ mkdir -p development/rtems
76  $ cd development/rtems
77  $ git clone git://git.rtems.org/rtems-source-builder.git rsb
78    ...
79  $ cd rsb
80  $ ./source-builder/sb-check
81    ...
82  $ cd rtems
83  $ ../source-builder/sb-set-builder \
84      --prefix=/usr/home/chris/development/rtems/5 5/rtems-sparc
85    ...
86
87Build the RTEMS Kernel (:ref:`rtems-kernel-install`) by cloning the repository,
88running the ``bootstrap`` procecure, building and finally installing the
89kernel:
90
91.. code-block:: shell
92
93  $ export PATH=$HOME/development/rtems/5/bin:$PATH
94  $ cd
95  $ cd development/rtems
96  $ mkdir kernel
97  $ cd kernel
98  $ git clone git://git.rtems.org/rtems.git rtems
99    ...
100  $ cd rtems
101  $ ./bootstrap -c && $HOME/development/rtems/rsb/source-builder/sb-bootstrap
102    ...
103  $ cd ..
104  $ mkdir erc32
105  $ cd erc32
106  $ $HOME/development/rtems/kernel/rtems/configure --prefix=$HOME/development/rtems/5 \
107                     --target=sparc-rtems5 --enable-rtemsbsp=erc32 --enable-posix
108    ...
109  $ make -j 8
110    ...
111  $ make install
112
113You can now build a third-party library or an application.
Note: See TracBrowser for help on using the repository browser.