OpenCores
URL https://opencores.org/ocsvn/openrisc_2011-10-31/openrisc_2011-10-31/trunk

Subversion Repositories openrisc_2011-10-31

[/] [openrisc/] [trunk/] [rtos/] [rtems/] [c/] [UPDATE_HELP] - Blame information for rev 496

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 30 unneback
#
2
# $Id: UPDATE_HELP,v 1.2 2001-09-27 11:59:11 chris Exp $
3
#
4
 
5
Between RTEMS 3.1.0 and 3.2.0, every RTEMS defined symbol made visible
6
was renamed.  This document describes the change and the tools provided
7
to 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
 
11
DESCRIPTION OF NAME CHANGES:
12
============================
13
 
14
The primary change was the addition of the prefix "rtems_" or "RTEMS_" to
15
EVERY user visible RTEMS provided constant and routine.  The primary
16
factor in the decision to make such a sweeping change was conflicts
17
between the the RTEMS and POSIX API's.
18
 
19
 
20
TO UPDATE YOUR APPLICATION:
21
===========================
22
 
23
The update script requires that Perl be installed on your computer.
24
It has only been tested with Perl 5.x.
25
 
26
After RTEMS has been built, in the directory "$r//update_tools", will
27
be a set of tools to aid in making the application source changes necessary
28
to address (hopefully) all of the name changes in the RTEMS API between
29
releases 3.1.0 and 3.2.0.
30
 
31
The update shell script is the only executable which is invoked by the
32
user directly.  The word-replace Perl script is invoked by the update
33
shell script.
34
 
35
WARNING: These tools modify the files IN PLACE!!! Backup your
36
         source before using these tools.
37
 
38
To udpate your application, change directories to the top of your application
39
source tree and execute the update script.  It should be something similar
40
to the following:
41
 
42
cd MY_APP
43
$r//update-tools/update
44
 
45
The update script will ask if you have backed up your source code before
46
beginning the update process.  While operating on files, it will print
47
the name of each file and a dot for each change made to the source file.
48
 
49
NOTE: 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.

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.