diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2019-01-23 10:40:40 +0100 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2019-01-24 07:31:25 +0100 |
| commit | 63735bc9d2ec845ebe070c9eb0bb45f60aefdebc (patch) | |
| tree | 7d522088c8fe1c090bcc975536dc151a4a89e7c5 /user/rsb | |
| parent | user: Stub documentation for griscv BSP (diff) | |
| download | rtems-docs-63735bc9d2ec845ebe070c9eb0bb45f60aefdebc.tar.bz2 | |
user: Spell out third-party
Diffstat (limited to 'user/rsb')
| -rw-r--r-- | user/rsb/third-party-packages.rst | 12 | ||||
| -rw-r--r-- | user/rsb/why-build-from-source.rst | 2 |
2 files changed, 7 insertions, 7 deletions
diff --git a/user/rsb/third-party-packages.rst b/user/rsb/third-party-packages.rst index a6a541b..82be4ff 100644 --- a/user/rsb/third-party-packages.rst +++ b/user/rsb/third-party-packages.rst @@ -2,19 +2,19 @@ .. Copyright (C) 2012, 2016 Chris Johns <chrisj@rtems.org> -RTEMS 3rd Party Packages +RTEMS Third-Party Packages ======================== -This section describes how to build and add an RTEMS 3rd party package to the +This section describes how to build and add an RTEMS third-party package to the RSB. -A 3rd party package is a library or software package built to run on RTEMS, +A third-party package is a library or software package built to run on RTEMS, examples are NTP, Net-Snmp, libjpeg or Python. These pieces of software can be used to help build RTEMS applications. The package is built for a specific BSP and so requires a working RTEMS tool chain and an installed RTEMS Board Support Package (BSP). -The RSB support for building 3rd party packages is based around the *pkconfig* +The RSB support for building third-party packages is based around the *pkconfig* files (PC) installed with the BSP. The pkgconfig support in RTEMS is considered experimental and can have some issues for some BSPs. This issue is rooted deep in the RTEMS build system. If you have any issues with this support please ask @@ -26,7 +26,7 @@ Vertical Integration The RSB supports horizontal integration with support for multiple architectures. Adding packages to the RSB as libraries is vertical integration. Building the GCC tool chain requires you build an assembler before -you build a compiler. The same can be done for 3rd party libraries, you can +you build a compiler. The same can be done for third-party libraries, you can crate build sets that stack library dependences vertically to create a *stack*. Building @@ -133,7 +133,7 @@ RTEMS. dynamic libraries are created and installed. The RSB provides the configuration file ``rtems/config/rtems-bsp.cfg`` to -support building 3rd party packages and you need to include this file in your +support building third-party packages and you need to include this file in your RTEMS version specific configuration file. For example the Net-SNMP configuration file ``rtems/config/net-mgmt/net-snmp-5.7.2.1-1.cfg``:: diff --git a/user/rsb/why-build-from-source.rst b/user/rsb/why-build-from-source.rst index 80aa329..5d88e0c 100644 --- a/user/rsb/why-build-from-source.rst +++ b/user/rsb/why-build-from-source.rst @@ -33,7 +33,7 @@ an equivalent tool set. Building from source provides you with control over the configuration of the package you are building. If all or the most important dependent parts are built from source you limit the exposure to host variations. For example the -GNU C compiler (gcc) currently uses a number of 3rd party libraries internally +GNU C compiler (gcc) currently uses a number of third-party libraries internally (gmp, mpfr, etc). If your validated compiler generating code for your target processor is dynamically linked against the host's version of these libraries any change in the host's configuration may effect you. The changes the host's |