mcp2make 1.0.2 (c) ARM Ltd 2003.




Changes from 1.0.1
==================
Generate correct object filenames for source files in subfolders.
Utilize system include paths from the CodeWarrior project.
Avoid duplicating entries in the dependancy list.
Generate correct dependancy lists when using RVCT.




Introduction
============
The version of CodeWarrior used in the ARM Development Suite
cannot export projects in makefile format. Manually producing
makefiles from CodeWarrior projects is not an easy task. The
aim of mcp2make is to make the conversion simpler and to require
substantially less effort.


mcp2make is supplied as a free-of-charge, unsupported utility.




Functional Overview
===================
CodeWarrior project files are stored in an undocumented binary
format which cannot be parsed directly by an external utility.
However, CodeWarrior does allow the export of a project file as a
separate XML text file, which is suitable for parsing by an 
external utility. mcp2make is such a utility.


This XML file contains most (but not all) of the information
relating to the build environment for that project. It includes
data on the different build targets, a list of the files used to
build the target and other helpful information. Thus mcp2make can
automatically generate the structure of an equivalent makefile.


However the XML file does not include the command line parameters
used for the code generation tools (C/C++ compilers, linker, 
etc.). This data must be manually copied from the appropriate
CodeWarrior "Equivalent Command Line" text boxes into mcp2make.


Each build target of the CodeWarrior project (e.g. Debug, 
DebugRel, Release) will generate a separate makefile.


Note that the expectation is that changing a CodeWarrior project
into a makefile is a once-only conversion and some minor manual
modifications of the makefile produced may still be needed in 
order to get it into the required state.




Using mcp2make
==============


Create the XML file
-------------------
First of all you need to create the XML version of the 
CodeWarrior project file. Unfortunately, CodeWarrior cannot
automate this step so the user is required to perform this
operation manually.


1. Open your project with CodeWarrior.
2. Choose File->Export Project... from the menu bar. This will
   present you with a save dialog box.
3. Save the XML file (with the .mcp.xml extension) in the same
   directory containing the CodeWarrior project file.




Converting the project
----------------------
Once you have an XML project file you can start mcp2make. This 
will present a simple dialog box allowing the user to specify
the XML project to convert. 


The basic steps for using mcp2make are:


    * select an XML file to convert
    * select a build target and specify the parameters to the
      code generation tools
    * create the makefile


1. Specify the XML project file to convert.
   You can either type a full path or use the Browse... button to
   choose the file from a standard file open dialog box. This 
   dialog box will remember the XML file used the previous time.


2. Click the OK button.
   This will parse the XML file and present a second dialog box
   for configuring each build target.


3. Select the desired build target from the Target Name popup
   menu.


4. Specify the parameters for each code generation tool used for
   the selected target.


   There is a text field for each codegen tool available
   (e.g. Assembler, Linker, etc.). The text field for each tool 
   is enabled if it is used in the current target - all other
   fields are disabled. 
   
   Each enabled text field needs to contain the command-line 
   parameters for that tool. You can find the command-line 
   parameters for a tool from the Equivalent Command Line text 
   box of its Settings Panel in the Project Settings dialog box.
   For example, to find the Assembler command-line for the Debug
   target:
a. Choose Debug from the Target menu of the project
  window.
b. Choose Edit->Debug Settings... from the menu bar.
c. Select the ARM Assembler Settings Panel.
d. Select all of the text from the Equivalent Command
  Line text field and Copy it to the clipboard.
e. Switch to mcp2make and Paste the text into the 
  Assembler text field.


5. Click the Create Makefile button.
   This will create a makefile named _.mk (e.g.
   MyProject_Release.mk) in the same directory as the project 
   file. During this process you will see a number of DOS boxes 
   quickly flash on the screen. This is mcp2make invoking the 
   compiler to find the header dependancies for each source
   file.


6. Repeat steps 3-5 for each target that you wish to produce a
   makefile for.