From adee597960ce3c5ff0ce303ae9ac25b7eebdfe32 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 4 May 2000 19:45:17 +0000 Subject: Numerous changes based on comments from Stephan Wilms including a new section in the Getting Started called "Where to Go From Here", lots of index entries added, and more configuration table information. --- doc/started/buildrt.t | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'doc/started/buildrt.t') diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t index e3d70efcab..d3d85c2401 100644 --- a/doc/started/buildrt.t +++ b/doc/started/buildrt.t @@ -102,6 +102,8 @@ tools/@value{RTEMS-UNTAR}/README.configure in the RTEMS source tree. If the BSP parameter is not specified, then all supported BSPs for the selected CPU family will be built. +@b{NOTE:} The POSIX API must be enabled to use GNAT/RTEMS. + @subsection Using the RTEMS configure Script Directly Make a build directory under tools and build the RTEMS product in this @@ -112,6 +114,10 @@ comes with the RTEMS distribution. In the installation described in the section "Unpack the RTEMS source", these configuration options can be found in the file tools/@value{RTEMS-UNTAR}/README.configure. +The GNAT/RTEMS run-time implementation is based on the POSIX API. Thus +the RTEMS configuration for a GNAT/RTEMS environment MUST include the +@code{--enable-posix} flag. + The following shows the command sequence required to configure, compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP, and C++ support disabled. RTEMS will be built to target -- cgit v1.2.3