Changeset cb4e4e2 in rtems-docs


Ignore:
Timestamp:
Jan 23, 2019, 1:33:35 PM (9 months ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
7ad2d12
Parents:
d7caf8a
git-author:
Sebastian Huber <sebastian.huber@…> (01/23/19 13:33:35)
git-committer:
Sebastian Huber <sebastian.huber@…> (02/18/19 13:41:09)
Message:

user: Remove obsolete content in quick start

File:
1 edited

Legend:

Unmodified
Added
Removed
  • user/start/index.rst

    rd7caf8a rcb4e4e2  
    2525    bsp-test
    2626    app
    27 
    28 The following is a quick start guide that provides a basic set of commands to
    29 build the RTEMS Tools and Kernel. The quick start guide provides links to the
    30 detailed sections if any problems are encountered.
    31 
    32 The detailed procedure for installing an RTEMS Workspace and installing
    33 all tools can be found in :ref:`installation`. This includes information
    34 on installation points, developer versions, and the RTEMS kernel.
    35 
    36 The 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 
    49 Each of these steps is described in a section in this guide.
    50 
    51 Creating a Workspace
    52 ====================
    53 
    54 Before beginning, the development host computer needs to be set up for
    55 this quick start procedure to complete successfully. :ref:`host-computer`
    56 details what is needed for the supported host operating systems. If
    57 Windows is being used it is recommended following the procedure in
    58 :ref:`microsoft-windows` first.
    59 
    60 There are many ways and locations a suitable environment can be set up. A
    61 common factor that defines the final location of tools and projects is the
    62 place you have suitable storage. Another is permissions.  There is no
    63 need to become root or the administrator and we recommend you avoid
    64 doing this. You can build and install the tools anywhere on the host's
    65 file system you, as a standard user, have read and write access too.
    66 :ref:`Prefixes` and :ref:`ProjectSandboxing` provide detailed examples
    67 of possible locations and set ups.
    68 
    69 Simple 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 
    87 Build the RTEMS Kernel (:ref:`rtems-kernel-install`) by cloning the repository,
    88 running the ``bootstrap`` procecure, building and finally installing the
    89 kernel:
    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 
    113 You can now build a third-party library or an application.
Note: See TracChangeset for help on using the changeset viewer.