![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Migrating Legacy C/C++ Code to Apex Contents Preface
- Audience
- Other Resources
- Apex Documentation Roadmap
- Contacting Rational Technical Publications
- Contacting Rational Technical Support
Migrating Legacy C/C++ Code to Apex
- Introduction
- Apex Architecture Control
- Apex Build Management
- Apex C/C++ Development Tools
- Third Party C/C++ Compiler Compatibility
- Using an External Library As Is
- Recommended Approach
- Apex C/C++ Model Based Approach
- Apex C/C++ Build Key Based Approach
- Migrating an External Library to an Apex View
- Migration Tools Overview
- Migrating to Apex Views by Reference
- Migrating to Apex Views by Copy
- Migration Tools
- dirmig - compose a directory migration map
- makemig - analyze makefiles for migration-relevant information
- filemig - define a full file migration map
- perfmig - test and perform migration steps
- subsysmig - test and perform subsystem decomposition step
- archmig - test and perform architectural control step
- vermig - test and perform version control step
- cleanmig - test and perform cleanup step
- duprefmig - duplicate a "migrate by reference" tower of views
- Full Migration Map Syntax
- Apex Commands Used During Migration
Migrating Legacy C/C++ Code to Apex Index
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |