| 1 |
# |
| 2 |
# README,v 1.2 2002/10/07 19:44:18 joel Exp |
| 3 |
# |
| 4 |
|
| 5 |
Building and Installing MDP & PROTOLIB for RTEMS |
| 6 |
===================================== |
| 7 |
|
| 8 |
1. Build and install RTEMS for your BSP with POSIX and networking |
| 9 |
enabled. The following is a prototypical command sequence that |
| 10 |
would be used to do this for the mips-rtems target and jmr3904 BSP. |
| 11 |
|
| 12 |
mkdir b-rtems |
| 13 |
cd b-rtems |
| 14 |
..../rtems-XXX/configure --target=mips-rtems --enable-rtemsbsp=jmr3904 \ |
| 15 |
--enable-posix --enable-networking --prefix=/opt/rtems |
| 16 |
make |
| 17 |
make install |
| 18 |
|
| 19 |
Once this is done, return to this directory and proceed with the |
| 20 |
MDP build. |
| 21 |
|
| 22 |
2. Set the RTEMS_MAKEFILE_PATH to point to the above BSP. |
| 23 |
|
| 24 |
export RTEMS_MAKEFILE_PATH=/opt/rtems/mips-rtems/jmr3904 |
| 25 |
|
| 26 |
3. To build the MDP and ProtoLib libraries, perform commands similar to |
| 27 |
the following: |
| 28 |
|
| 29 |
export RTEMS_MAKEFILE_PATH=/opt/rtems/mips-rtems/jmr3904 |
| 30 |
cd mdp |
| 31 |
make -f Makefile.rtems libs_only |
| 32 |
|
| 33 |
At this point you should have libProto.a and libMdp.a. Copy them to |
| 34 |
the appropriate BSP specific install point by hand. |
| 35 |
|
| 36 |
|
| 37 |
Integrating NTP Executables Into Your Application |
| 38 |
================================================= |
| 39 |
No RTEMS specific steps are required to use the MDP library. |
| 40 |
|
| 41 |
Port Background |
| 42 |
=============== |
| 43 |
The RTEMS port is derived from the UNIX source base. The |
| 44 |
MDP package includes example applications that cannot be |
| 45 |
built for RTEMS as they depend upon X11 and Tk. Thus the |
| 46 |
port includes only the MDP communications protocol. |
| 47 |
|
| 48 |
The RTEMS port assumes that Protolib and MDP will be built for |
| 49 |
a particular BSP which has been previously built and |
| 50 |
installed. Two RTEMS specific sub-Makefiles have been added |
| 51 |
to the unix/ subdirectory of each package. |
| 52 |
|
| 53 |
+ Makefile.rtems |
| 54 |
+ Makefile.rtems-sub |
| 55 |
|
| 56 |
Makefile.rtems acts as the normal MDP/Protolib adapter. |
| 57 |
Makefile.rtems-sub acts as a query facility to obtain |
| 58 |
information from the RTEMS Application Makefile |
| 59 |
infrastructure. By using this approach, the MDP/Protolib |
| 60 |
libraries should be able to be compiled for any RTEMS BSP. |
| 61 |
|
| 62 |
Protolib/MDP Assembly Instructions |
| 63 |
================================== |
| 64 |
The RTEMS MDP/Protolib tarball was assembled from separate |
| 65 |
MDP and Protolib tarballs which were combined to provide |
| 66 |
a unified build process. These instructions are based |
| 67 |
upon the following versions: |
| 68 |
|
| 69 |
src-mdp-1.9a5.tgz |
| 70 |
src-protolib-1.0a3d.tgz |
| 71 |
|
| 72 |
1. Make a working directory and "cd" into that directory. |
| 73 |
2. untar mdp and protolib |
| 74 |
3. If mdp/protolib exists and is a symbolic link, then remove it. |
| 75 |
4. mv protolib under mdp (mv protolib-1.0 mdp) |
| 76 |
These results in the following directory structure. |
| 77 |
|
| 78 |
./mdp |
| 79 |
./mdp/protolib |
| 80 |
|