source: rtems/doc/FAQ/freesw.t @ 0ab65474

4.104.114.84.95
Last change on this file since 0ab65474 was 0ab65474, checked in by Joel Sherrill <joel.sherrill@…>, on Jun 10, 2000 at 8:33:47 PM

Purged as many egcs references as possible.

  • Property mode set to 100644
File size: 5.2 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1999.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9@chapter Free Software that Works with RTEMS
10
11This section describes other free software packages that are known to work
12with RTEMS.
13
14@section Development Tools
15
16@subsection Basic Development Environment
17
18The standard RTEMS development environment consists of the following GNU
19components:
20
21@itemize @bullet
22
23@item gcc
24@item binutils
25@item gdb
26
27@end itemize
28
29Although not from the Free Software Foundation, the Cygnus newlib C
30library integrates well with the GNU tools and is a standard part of the
31RTEMS development environment.
32
33@subsection GNU Ada
34
35For those interested in using the Ada95 programming language, the GNU Ada
36compiler (GNAT) is available and has excellent support for RTEMS.
37
38@subsection DDD - Data Display Debugger
39
40By far the easiest way to use DDD if you are on a Redhat or SuSE Linux system
41is to retrieve the RPM package for your OS version.  In general, it is
42easier to install a static binary since doing so avoids all problems
43with dynamic library versions.
44
45Some versions of DDD have had trouble with Lesstif.  If you
46are using Lesstif, you will need version 0.88 or newer.  It
47is also available as an RPM at the popular sites.  Another Motif
48clone is Motive and versions 1.2 and newer known to work with DDD
49on popular distributions of Linux including RedHat and Slackware.
50
51Installed as RPMs, DDD in conjunction with either Lesstif or Motive
52should work out-of-the-box.
53
54User comments indicate that both Lesstif and DDD can be built
55from scratch without any problems.  Instructions on installing DDD
56are at @uref{http://www.cs.tu-bs.de/softech/ddd/}.  They
57indicate that
58
59@itemize @bullet
60LessTif should be used in (default) Motif 1.2 compatibility mode.
61
62The Motif 2.0 compatibility mode of LessTif is still incomplete.
63@end itemize
64
65So configure lesstif with --enable-default-12.
66
67The configure script is broken (see  www.lesstif.org --> known problems)
68for 0.88.1. I didn't fix the script as they show, so I just have links
69in /usr/local/lib (also shown).
70
71Watch out: Lesstif installs its libraries in /usr/local/Lesstif. You
72will need to update /etc/ld.so.conf and regenerate the cache of shared
73library paths to point to the Motif 1.2 library.
74
75The following notes are from an RTEMS user who uses DDD in conjunction
76with Lesstif.  Configure DDD "--with-motif-libraries=/usr/local/lib
77--with-motif-includes=/usr/local/include" DDD needs gnuplot 3.7. 
78@uref{ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot-3.7.tar.gz}. Build and
79install from scratch. 
80
81DDD can be started from a script that specifies the cross debugger.
82This simplifies the invocation.  The following example shows what
83a script doing this looks like.
84
85@example
86#!/bin/bash
87ddd --debugger m68k-elf-gdb $1
88@end example
89
90Under many flavors of UNIX, you will likely have to relax permissions.
91
92On Linux, to get gdb to use the serial ports while running as a
93normal user, edit /etc/security/console.perms, and create a <serial>
94class (call it whatever you want).
95
96@example
97<serial>=/dev/ttyS* /dev/cua*
98@end example
99
100Now enable the change of ownership of these devices when users log in
101from the console:
102
103@example
104<console> 0600 <serial> 0600 root
105@end example
106
107Users report using minicom to communicate with the target to initiate a TFTP
108download. They then suspend minicom, launch DDD, and begin debugging.
109
110The procedure should be the same on other platforms, modulo the choice
111of terminal emulator program and the scheme used to access the serial
112ports. From problem reports on the cygwin mailing list, it appears that
113GDB has some problems communicating over serial lines on that platform.
114
115NOTE: GDB does not like getting lots of input from the program under test
116over the serial line. Actually, it does not care, but it looses
117characters. It would appear that flow control is not re-enabled when it
118resumes program execution. At times, it looked like the test were
119failing, but everything was OK. We modified the MVME167 serial driver to
120send test output to another serial port.  Using two serial ports is
121usually the easiest way to get test output while retaining a reliable debug
122connection regardless of the debugger/target combination.
123
124NOTE: Enabling gdb's remote cache might prevent this (Observed with SH1
125boards, but may also be valid for targets):
126@example
127gdb > set remotecache
128@end example
129
130Information provided by Charles-Antoine Gauthier (charles.gauthier@@iit.nrc.ca)
131Jiri Gaisler (jgais@@ws.estec.esa.nl) and Ralf Cors@'epius
132(corsepiu@@faw.uni-ulm.de)
133
134
135@section omniORB
136
137omniORB is a GPL'ed CORBA which has been ported to RTEMS.  It is
138available from
139(@uref{http://www.uk.research.att.com/omniORB/omniORB.html,http://www.uk.research.att.com/omniORB/omniORB.html})
140.
141
142For information on the RTEMS port of omniORB to RTEMS, see the following
143URL
144(@uref{http://www.connecttel.com/corba/rtems_omni.html,http://www.connecttel.com/corba/rtems_omni.html}).
145
146C++ exceptions must work properly on your target for omniORB to work.
147
148The port of omniORB to RTEMS was done by Rosimildo DaSilva
149<rdasilva@@connecttel.com>. 
150
151@section TCL
152
153Tool Command Language.
154
155ditto
156
157@section ncurses
158
159Free version of curses.
160
161ditto
162
163
164@section zlib
165
166Free compression/decompression library.
167
168ditto
169
Note: See TracBrowser for help on using the repository browser.