![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: RiC++ 4.0 ETSAdapter Topic Summary: Created On: 27-Sep-2005 21:01 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|||
ReadMe for VentureCom (a.k.a. Phar Lap) ETS ver. 10.1 OS Adapter for Rhapsody 4.0
======================================================================================= Note: The enclosed adapter is for C++ language using Microsoft Visual C++ compiler only. (for x86 targets) CONTENTS: 1. etsmake.bat - Master batch file for making all the ETS libraries for Rhapsody 2. etsmakeboot.bat - Utility for creating a linkloc linker control file & boot disk for target 3. Rhapsody framework libraries for VentureCom ETS ver. 10.1 4. Custom makefiles for the ETS adapter 5. Custom framework C++ file(s) for the ETS adapter 6. siteC++.prp - Custom configuration file for the ETS adapter Installation Procedures for ETS Adapter 4.0 ================================================ Step 1 Copy ETS adapter over to existing Rhapsody Installation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Copy the entire contents of the ETS adapter "share" directory and drop it over on top of the existing Rhapsody 3.0/3.0.1 share directory on your installation. The appropriate files will be added or overwritten to the share directory and any subdirectories within it. If any of the files in the Rhapsody installation that are being overwritten are write protected, then write protection must be removed prior to transfering. Caution: If you have an existing custom siteC++.prp file in your Rhapsody installation, you will need to "merge"the contents of the \share\properties\siteC++.prp file in this adapter with your customized siteC++.prp file. The procedure above assumes you have no valuable siteC++.prp file existing. Step 2 Copy utility file over to ETS directory and verify paths ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Copy the batch file "share\etc\etsmakeboot.bat" found in this adapter over the ETS \bin directory. If not already set, verify the environment path is set to find the ETS \bin directory. (e.g. c ![]() Step 3 Set the ETS installation directory ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The batch file "share\etc\etsmake.bat" found in this adapter installation contains an environment variable that points to the ETS installation on your system. By default it points to c:\pharemb If this is correct, no further action is required. If not, then edit "etsmake.bat" line 4 to the correct ETS root directory. The same must be done for the batch file "etsmakeboot.bat". Step 4 Creating a linker control file ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Before Rhapsody builds can be linked, it is necessary to create a linker control file for ETS's "linkloc" linker to use when the build command is launched from within Rhapsody. Rhapsody will try to find an appropriate linker control file in the \bin directory of the ETS installation (e.g. c:\pharemb\bin, by default). The linker control file that Rhapsody tries to use has a fixed name(s) : "etsdev.lcf" for debug versions of your builds and "etsdevr.lcf" for release versions. Since the embedded target is usually a fixed HW configuration, this fixed name for the linker control file makes it easy to change project names with Rhapsody without have to recreate a new linker control file every time. ETS uses a "matched" set for the linker control files used for building the ETS kernel/monitor and the linker control file used to build an ETS application. Therefore, a utitlity batch file was created that performs the following actions: a) Creates a linker control file called "etsdev.lcf" if fed a file name of a *.lnk file or b) Creates a linker control file called "etsdevr.lcf" if fed a file name of a *.lnk file and an "r" argument. c) Creates a boot monitor disk on drive A: For example, to create a debug linker control file for Rhapsody from "PC104.lnk" and "PC104.lkr" files created from a Visual System builder file "PC104.vsb", type "etsmakeboot PC104" from within the directory containing the linker control files. To create a release version of the same linker control files, type "etsmakeboot PC104 r" instead. In both cases, a new kernel/monitor boot disk will be created on drive A:
|
|||
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.