Changeset 63735bc in rtems-docs


Ignore:
Timestamp:
Jan 23, 2019, 9:40:40 AM (3 years ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
5, am, master
Children:
3db6371
Parents:
5973f92
git-author:
Sebastian Huber <sebastian.huber@…> (01/23/19 09:40:40)
git-committer:
Sebastian Huber <sebastian.huber@…> (01/24/19 06:31:25)
Message:

user: Spell out third-party

Location:
user
Files:
11 edited

Legend:

Unmodified
Added
Removed
  • user/exe/executables.rst

    r5973f92 r63735bc  
    2020executables. The tool chain executable creates a fixed position statically
    2121linked Extendable Loader Format (ELF) file that contains the RTEMS kernel,
    22 standard libraries, 3rd party libraries and application code. RTEMS executes in
     22standard libraries, third-party libraries and application code. RTEMS executes in
    2323a single address space which means it does not support the ``fork`` or ``exec``
    2424system calls so statically linking all the code is the easiest and best way to
     
    5151and Ada.
    5252
    53 Applications are built from source into ELF object files, 3rd party packages
     53Applications are built from source into ELF object files, third-party packages
    5454can be built as libraries or they can be imported as source into an application
    55 code base. The application, 3rd party packages, RTEMS and standard libraries
     55code base. The application, third-party packages, RTEMS and standard libraries
    5656are linked to create the RTEMS executable. The executable is transferred to the
    5757target and a bootloader loads it from the non-volatile storage into RAM or the
     
    6868   Building an Application
    6969
    70 The standard and 3rd party libraries are a collection of object files built
     70The standard and third-party libraries are a collection of object files built
    7171using the same set of tools the application source is compiled with. The
    7272package collects it's object files into an archive or library.
  • user/hardware/targets.rst

    r5973f92 r63735bc  
    1313executable is statically linked and executes in a single address space on the
    1414target hardware. A statically linked executable means the RTEMS Kernel,
    15 drivers, third party packages and application code is linked into a single
     15drivers, third-party packages and application code is linked into a single
    1616executable image. A single address space means no virtual memory and no memory
    1717protected process address space is running within the RTEMS arena and the RTEMS
  • user/hosts/macos.rst

    r5973f92 r63735bc  
    3131these tools from a packaging tool for MacOS such as *MacPorts* or *HomeBrew*.
    3232
    33 I do not use 3rd party packaging on MacOS and prefer to build the packages from
    34 source using a prefix of ``/usr/local``. There are good 3rd party packages around
     33I do not use third-party packaging on MacOS and prefer to build the packages from
     34source using a prefix of ``/usr/local``. There are good third-party packages around
    3535however they sometimes bring in extra dependence and that complicates my build
    3636environment and I want to know the minimal requirements when building
  • user/hosts/windows.rst

    r5973f92 r63735bc  
    7272
    7373Building the RTEMS compilers, debugger, the RTEMS kernel and a number of other
    74 3rd party packages requires a POSIX environment. On Windows you can use Cygwin
     74third-party packages requires a POSIX environment. On Windows you can use Cygwin
    7575or MSYS2. This document focuses on MSYS2. It is smaller than Cygwin and comes
    7676with the Arch Linux package manager ``pacman``.
     
    214214virus detection tool installed and enabled. The excellent ``Process Hacker 2``
    215215tool can monitor the performance and the Windows Defender service contributed a
    216 high load. In this case a 3rd party virus tool was installed so the Windows
     216high load. In this case a third-party virus tool was installed so the Windows
    217217Defender service was not needed.
    218218
  • user/installation/releases.rst

    r5973f92 r63735bc  
    285285 Build Set: Time 0:19:15.713662
    286286
    287 You can now build a 3rd party library or an application as defaulted in TBD.
     287You can now build a third-party library or an application as defaulted in TBD.
  • user/overview/index.rst

    r5973f92 r63735bc  
    249249RTEMS is an open source operating system and an open source project and this
    250250extends to the ecosystem. We encourage users to integrate the processes to
    251 build tools, the kernel and any 3rd party libraries into their project's
     251build tools, the kernel and any third-party libraries into their project's
    252252configuration management processes.
    253253
  • user/rsb/third-party-packages.rst

    r5973f92 r63735bc  
    33.. Copyright (C) 2012, 2016 Chris Johns <chrisj@rtems.org>
    44
    5 RTEMS 3rd Party Packages
     5RTEMS Third-Party Packages
    66========================
    77
    8 This section describes how to build and add an RTEMS 3rd party package to the
     8This section describes how to build and add an RTEMS third-party package to the
    99RSB.
    1010
    11 A 3rd party package is a library or software package built to run on RTEMS,
     11A third-party package is a library or software package built to run on RTEMS,
    1212examples are NTP, Net-Snmp, libjpeg or Python. These pieces of software can be
    1313used to help build RTEMS applications. The package is built for a specific
     
    1515Support Package (BSP).
    1616
    17 The RSB support for building 3rd party packages is based around the *pkconfig*
     17The RSB support for building third-party packages is based around the *pkconfig*
    1818files (PC) installed with the BSP. The pkgconfig support in RTEMS is considered
    1919experimental and can have some issues for some BSPs. This issue is rooted deep
     
    2727architectures. Adding packages to the RSB as libraries is vertical
    2828integration. Building the GCC tool chain requires you build an assembler before
    29 you build a compiler. The same can be done for 3rd party libraries, you can
     29you build a compiler. The same can be done for third-party libraries, you can
    3030crate build sets that stack library dependences vertically to create a *stack*.
    3131
     
    134134
    135135The RSB provides the configuration file ``rtems/config/rtems-bsp.cfg`` to
    136 support building 3rd party packages and you need to include this file in your
     136support building third-party packages and you need to include this file in your
    137137RTEMS version specific configuration file. For example the Net-SNMP
    138138configuration file ``rtems/config/net-mgmt/net-snmp-5.7.2.1-1.cfg``::
  • user/rsb/why-build-from-source.rst

    r5973f92 r63735bc  
    3434package you are building. If all or the most important dependent parts are
    3535built from source you limit the exposure to host variations. For example the
    36 GNU C compiler (gcc) currently uses a number of 3rd party libraries internally
     36GNU C compiler (gcc) currently uses a number of third-party libraries internally
    3737(gmp, mpfr, etc). If your validated compiler generating code for your target
    3838processor is dynamically linked against the host's version of these libraries
  • user/start/index.rst

    r5973f92 r63735bc  
    105105  $ make install
    106106
    107 You can now build a 3rd party library or an application.
     107You can now build a third-party library or an application.
  • user/tools/index.rst

    r5973f92 r63735bc  
    77
    88The RTEMS kernel is developed on host computers cross-compiled and linking the
    9 kernel, language runtime libraries, 3rd party packages and application source
     9kernel, language runtime libraries, third-party packages and application source
    1010code so it can run on target hardware. RTEMS and some of the hardware it
    1111support cannot self-host so we need a range of tools to support the wide range
  • user/tracing/index.rst

    r5973f92 r63735bc  
    1010
    1111RTEMS Tracing Framework is an on-target software based system which helps track
    12 the ongoings inside the operation of applications, 3rd party packages, and the
     12the ongoings inside the operation of applications, third-party packages, and the
    1313kernel in real time.
    1414
Note: See TracChangeset for help on using the changeset viewer.