Inside Macintosh: Programmer's Guide to MacApp / Part 2 - Working With MacApp

Appendix A - Working With the MacApp Build System

Outputs

The MABuild process creates a makefile called YourApp.MakeIt. It also creates object files for your code and for MacApp's code, an executable version of your application, and a folder in which the other files are stored.

The YourApp.MakeIt script contains the commands that were executed by the build. You should not simply execute this file again when you need to rebuild. Instead, run MABuild again so it can determine what must be rebuilt.

Folder-Naming Convention

Where does MABuild put all the files it generates? It puts the file YourApp.MakeIt (containing the output of the MABuild process), along with the object code files, executable application file, and symbol file (if any), in a folder in the directory specified by the options in the MABuild command. This folder is normally a subdirectory of the application's source code folder.

If you use the -autoBuild option to build MacApp along with your application, MABuild creates a similarly named library folder for each variation of MacApp in MacApp's library directory, referred to by the shell variable {MALibraries}.

MacApp has many compile-time variables that you can set with MABuild's flag options. By default, MABuild creates a separate folder named after the options you choose, prepended by a character determined by the MPW shell variable MASeparateObjectsPrefix. For example, if you specify the options -nodebug, -sym, the output goes in a folder named (depending on the character specified by MASeparateObjectsPrefix)

%S7TeSmClSC

MABuild names the folders in which it keeps these separate versions using a convention that assigns a two-character mnemonic based on the value of each compile-time flag, as shown in Table A-3. Then it strings together all the pairs to produce one long name.

The name constructed from the string of mnemonic pairs indicates exactly what's in the folder, but it's not easily parsed by human eyes. MABuild offers an option (the RenameFlag option) that lets you give any name you like to any set of flags. In fact, the file {MATools}MABuild.r defines remappings for many sets of sets of flags, including those shown in Table A-4. As a result, for the options -nodebug, -sym, the real name of the output folder is (depending on the character specified by MASeparateObjectsPrefix)

%68K Sym

You can define other names using the RenameFlag option on the MABuild command line. Or you can modify the definition of MABuildDefaults in the 1Startup file by adding lines such as the following (a made-up example, which remaps S7CqTeMr to NoDebug MrC Special instead of NoDebug MrC):

-RenameFlag S7CqTeMr 'NoDebug MrC Special'

You can also modify the 'STR#'(1000) RenameFlags resource in the MABuild tool. This is more efficient than adding rename flags in MABuildDefaults or on the command line.

Table A-3 Compiler option mnemonics

Code	Mnemonic for	Compiler option flag
20	Requires 68020 CPU	qNeedsMC68020
30	Requires 68030 CPU	qNeedsMC68030
40	Requires 68040 CPU	qNeedsMC68040
CF	Requires Code Fragment Manager	qModelCFM
Cl	Requires classic 68K runtime support	qClassic
Cq	Requires Color QuickDraw	qNeedsColorQD
Db	Basic debugging support	qDebug
Dm	Turn on debugging messages	qDebugMsg
fCfD	Far code and data models	qModelFarData, qModelFarCode
Fp	Require 68881 or 68882 coprocessor	qNeedsFPU
In	Inspector window support	qInspector
J	Support for Jasik's debugger	qTheDebugger
M8	Build with Metrowerks C/C++ compiler for 68K	No flag defined by MacApp; define __MWERKS__ in your code
Mr	Build with MrC compiler	No flag defined by MacApp
MW	Build with Metrowerks C/C++ compiler for Power Macintosh	No flag defined by MacApp; define __MWERKS__ in your code
Pe	Performance monitoring support	qPerform
Ra	Do range checking	qRangeCheck
S7	Requires System 7 or later	SystemSevenOrLater
SC	Build with Symantec C++ compiler (SCpp)	No flag defined by MacApp
Sm	SADE and SourceBug support	qSym
Te	Template views support	qTemplateViews
Vu	Requires Virtual User support	qNeedsVU
Wr	Writing template views support	qWriteTemplateViews

You don't normally change the default setting for the SeparateObjects option, but if for some reason you do not want to keep separate builds in separate folders, you can specify -NoSeparateObjects on the MABuild command line.

Table A-4 MABuild remapped names

Compiler mnemonic	New (remapped) name
S7CqTeMr	MrC
S7CqTeSmMr	MrC Sym
S7TeSmClSC	68K Sym
S7CqDbDmRaTeSmMr	MrC Debug
S7NmDbDmPeRaTeSmfCfDClSC	68K Debug Far