Tools
CodeWarrior Pro 2
Yes, we're using relatively old tools for this project. Why? Because Pete can't get the debugger from Pro 3 or Pro 4 to work properly on his system. We're hoping Pro 5 takes care of this problem.
Universal Headers 3.2
By contrast, we're using the totally whiz-bang brand-spankin'-new Universal Headers 3.2. (Sometimes we even use the Carbon headers, but you don't need to worry about that unless you want to.)
If you've read the Universal Headers 3.2 READ ME, you may remember that it claims that CodeWarrior Pro 4 includes Universal Headers 3.2. Unfortunately, at the last second, schedules zigged where they should have zagged and made a liar out the READ ME in question. So we couldn't use a stock Pro 4 even if the debugger did work on Pete's system.
Integration
We're hoping CW Pro 5 has Universal Headers 3.2 and a fixed debugger. Until then, we're using a bizarre mutant version of CW Pro 2 with Universal Headers 3.2. If you're lucky, you already have an environment which will build MIB. (If you're working with Carbon, this is more than likely.) But, in case you need to put something together, here's how we did ours.
- Install CodeWarrior Pro 2. Don't bother installing PowerPlant or MSL unless you have some need for them other than MIB. If you already have a CW Pro 2 folder, it might be faster to duplicate this folder than to install another. But, in any case, make sure you have a CW Pro 2 folder you don't need for anything else, because we'll be doing some major surgery.
- Here's the scary part: move the "Mac OS Support" folder onto the desktop. Make a new folder in your CW Pro 2 folder called "Mac OS Support".
- Find a copy of Universal Interfaces 3.2. Drop it into the new "Mac OS Support" folder.
- Try to build the parts of MIB you care about. If you want to get it all building, a good candidate project is
:MIB-Libraries:MoreIsBetterLib.mcp
.
- You'll get all sorts of errors, of course. Move the files you need out of the "Mac OS Support" folder you've left on the desktop and into the "Mac OS Support" folder in your CW Pro 2 folder.
On another page, we've included an abbreviated listing of the files in our "Mac OS Support" folder. This should help you if you run into trouble.
Building
As long as you preserve the relative position of the folders as originally distributed with the MIB package, you should have no trouble building any part of MIB with a properly integrated tool set as described above. The access paths should all be set up relative to the projects. If you run into trouble with missing files, the most common access path you'll need to set up is
":MIB-Libraries:
"; this is where all the library code lives, and the various clients (demos, etc.) don't use each others' code, so you should be able to concentrate on getting one client at a time to build.