Target MacOS

From Lazarus wiki
Revision as of 19:59, 9 December 2012 by MarkMLl (talk | contribs) (→‎Assembling and linking step on Mac OS: Start updating for 2012.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Is the target for classic MacOS, that is the predecessor to MacOS X. For MacOS X see Target Darwin.

Compiling in MPW

Free Pascal can now be used in the MPW development environment.

Free Pascal for MPW do call assembler and linker via ToolServer. This means you need ToolServer installed. This will normally not be an issue, since ToolServer is included in the MPW distribution.

At rare occasions you might get the error message "Cant call the assembler, switching to external assembler." I do not know the origin of this, but it will help to restart. On Mac OS X you might need to restart even Mac OS X. It might also indicate that you need to increase the memory setting for ToolServer.

Another workaround for such problems is to let the compiler write out an MPW-script (option -s), which when executed (in MPW) will assemble and link. This method can also be used if the compiler is to be called from a third program, to overcome the deadlock situation mentioned below under Dos.Exec.

For crosscompiling e. g. from Mac OS X to Mac OS, see below.

Some tips

Choosing apptype

For casual users, copying pascal text only programs from a book, APPTYPE CONSOLE is appropriate.

If you want an MPW tool, use $APPTYPE TOOL.

For maximum portability, the following:


... ensures it will be an MPW tool on MacOS, and a console application in Delphi where APPTYPE TOOL is not recognized.


From 24-01-2004 mac style resources can be included with {$R <resfile>}. If the resource file ends with .r it is considered a Rez type resource file (in text form). For all other files (including .rsrc), binary resources are assumed. Several resource files can be included.

Error messages

Errors, warnings, hints etc messages outputed by the compiler, is in MPW format, that is you can execute them and the error location will be displayed.


The procedure Dos.Exec is used to execute other programs. In MacOS this is supported, and the programs which can be executed is MPW tools. An AppleEvent is sent to ToolServer which in turn executes the tool. A limitation is that ToolServer is not reentrant, so if a program which is called via Dos.Exec, in turn call Dos.Exec, it will be deadlocked.

Assembler symbols

Internal symbols in the generated assembler files will have an lowercase "s" as part separator instead of "$". The reason is that PPCAsm does not support $.

QuickDraw globals

There is a variable qd defined in System.pp for use as the QuickDraw global.

For APPTYE TOOL and APPTYPE CONSOLE it is initialized, but for APPTYPE GUI you have to initialize it yourself.


See MPW debugging

Global variables

Currently all global variables are indirect, that is the entry in the TOC is always a pointer to data. (In the future small data items may be stored directly in the TOC)

Thus all references to globals are via a construct like: lwz rX, yyy[TC](r2) ;loads a pointer to a global into rX

Cross compiling from Mac OS X to Mac OS

Although not necessary nowadays when there exists a native compiler for target MacOS, her is some info on how to cross compile. See also Link on target.

Crosscompiling step on Mac OS X

When compiling, add these options:

 -Tmacos # target macos
 -st	 # dont generate executable, link on target

If make is used, add OPT=-st OS_TARGET=macos

Note that one must first build the RTL by issuing make in rtl/macos, with the above options, to be able to build other programs. The RTL must then be assembled and linked (see below) before comiling any program, otherwise the search paths in the link script will not be correct.

You might also want to add option -a, then the link script will not delete not needed files, in particular the assembler files (*.s). This can be useful if there are problems with the link scripts and you want to rerun it.

Assembling and linking step on Mac OS

In case that host and target machine is different, transfer the produced files, that is assembler files (*.s) and link script *_ppas, to the host.

In Mac OS, use MPW to assemble and link the output from FreePascal by executing the link script (which is an MPW script), with its directory as current directory. Unfortunately the link script does obtain the proper mac file type, so this has to be fixed first e. g with the MPW command SetFile.

Example: To build Hello World (together with the rtl unit system.pp), execute:

 Directory HD:Projekt:FreePascal:fpc:rtl:macos
 SetFile -c 'MPS ' -t 'TEXT' system_ppas
 system_ppas	#executes the script
 Directory HD:Projekt:FreePascal:fpc:demo:text
 SetFile -c 'MPS ' -t 'TEXT' hello_ppas
 hello_ppas	#executes the script

Above circa 2004/5.

Working notes: situation as of late 2012

The objective here is to build PPC and possibly 69K compilers, first as cross-compilers to run on a PC and then to run natively on MacOS v9. Part of the incentive for this is to investigate whether a PPC Mac, e.g. my (MarkMLl) G3 beige with "Old World" ROMs, is a usable testbed for the fixed 68K compiler which Sven has added to trunk at around 2.8.

On e.g. Debian Linux, build and install cross-binutils:

tar xjf binutils-2.20.1.tar.bz2
cd binutils-2.20.1
./configure --prefix=/usr/local/powerpc-linux powerpc-linux-gnu
sudo make install
sudo ln -s /usr/local/powerpc-linux/bin/as /usr/local/bin/powerpc-linux-as
sudo ln -s /usr/local/powerpc-linux/bin/ld /usr/local/bin/powerpc-linux-ld
sudo ln -s /usr/local/powerpc-linux/bin/ar /usr/local/bin/powerpc-linux-ar
sudo ln -s /usr/local/powerpc-linux/bin/objdump /usr/local/bin/powerpc-linux-objdump
sudo ln -s /usr/local/powerpc-linux/bin/objcopy /usr/local/bin/powerpc-linux-objcopy
sudo ln -s /usr/local/powerpc-linux/bin/strip /usr/local/bin/powerpc-linux-strip
powerpc-linux-ld -V

Do the same for m68k-linux-gnu.

Build a cross-compiler to run on a PC but targeting PPC:

cd /usr/local/src/fpc/fpc-trunk
export PP=
make "OPT=-O- -g" -C compiler powerpc
mv compiler/ppcppc compiler/ppcXppc

Renaming the compiler prevents it from being deleted by make clean etc., consider extending that OPT setting with -dEXTDEBUG.

Build a native RTL and compiler:

export PP=/usr/local/src/fpc/fpc-trunk/compiler/ppcXppc
make CPU_TARGET=powerpc OS_TARGET=linux rtl
make CPU_TARGET=powerpc OS_TARGET=linux compiler

Take a look at what we've got:

file compiler/ppcppc
compiler/ppcppc: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), statically linked, stripped
file rtl/units/powerpc-linux/system.o
rtl/units/powerpc-linux/system.o: ELF 32-bit MSB relocatable, PowerPC or cisco 4500, version 1 (SYSV), not stripped