source: rtems/c/UPDATE_HELP @ 5b9d6ddf

4.104.114.84.95
Last change on this file since 5b9d6ddf was 88d594a, checked in by Joel Sherrill <joel.sherrill@…>, on 05/24/95 at 21:39:42

Fully tested on all in-house targets

  • Property mode set to 100644
File size: 1.9 KB
Line 
1#
2# $Id$
3#
4
5Between RTEMS 3.1.0 and 3.2.0, every RTEMS defined symbol made visible
6was renamed.  This document describes the change and the tools provided
7to assist you in updating your RTEMS 3.1.0 application. 
8
9[NOTE:  This change was not included in snapshots prior to 3.1.15.]
10
11DESCRIPTION OF NAME CHANGES:
12============================
13
14The primary change was the addition of the prefix "rtems_" or "RTEMS_" to
15EVERY user visible RTEMS provided constant and routine.  The primary
16factor in the decision to make such a sweeping change was conflicts
17between the the RTEMS and POSIX API's. 
18
19
20TO UPDATE YOUR APPLICATION:
21===========================
22
23The update script requires that Perl be installed on your computer.
24It has only been tested with Perl 5.x.
25
26After RTEMS has been built, in the directory "$r/<BSP>/update_tools", will
27be a set of tools to aid in making the application source changes necessary
28to address (hopefully) all of the name changes in the RTEMS API between
29releases 3.1.0 and 3.2.0.
30
31The update shell script is the only executable which is invoked by the
32user directly.  The word-replace Perl script is invoked by the update
33shell script.
34
35WARNING: These tools modify the files IN PLACE!!! Backup your
36         source before using these tools.
37
38To udpate your application, change directories to the top of your application
39source tree and execute the update script.  It should be something similar
40to the following:
41
42cd MY_APP
43$r/<BSP>/update-tools/update
44
45The update script will ask if you have backed up your source code before
46beginning the update process.  While operating on files, it will print
47the name of each file and a dot for each change made to the source file. 
48
49NOTE: These scripts do not attempt to address changes in calling
50      sequences.  After the script has run, you will need to update
51      calls to rtems_clock_get(), rtems_timer_fire_after(), and
52      rtems_timer_fire_when() by hand.
Note: See TracBrowser for help on using the repository browser.