Target MacOS: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		(Mac OS Classic only)
2	2
3	3		MacOS is the target for Mac OS Classic, i.e. the predecessor to macOS. macOS itself was previously marketed as Mac OS X and OS X. For macOS, see [[Target Darwin]].
4	4
5	5		## Compiling in MPW
6	6
7	7		Free Pascal can now be used in the [[MPW]] development environment.
8	8
9	9		Free Pascal for MPW call assembler and linker via ToolServer. This means that you need ToolServer installed. This will normally not be an issue, since ToolServer is included in the MPW distribution.
10	10
11	11		In rare instances, you might get the error message "Can't 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 OSX. It might also indicate that you need to increase the memory setting for ToolServer.
12	12
13	13		Another workaround for such problems is to let the compiler write out an MPW script (option -s). This will assemble and link when executed in MPW. 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.
14	14
15	15		For crosscompiling e.g. from macOS to Mac OS Classic, see below.
16	16
17	17		## Some tips
18	18
19	19		### Choosing apptype
20	20
21	21		For casual users, copying Pascal text only programs from a book, `{$APPTYPE CONSOLE}` is appropriate.
22	22
23	23		If you want an MPW tool, use `{$APPTYPE TOOL}`.
24	24
25	25		For maximum portability, the following:
26	26
27		-	~~` {$IFDEF MACOS}`\~~
28		-	~~` {$APPTYPE TOOL}`\~~
29		-	~~` {$ELSE}`\~~
30		-	~~` {$APPTYPE CONSOLE}`\~~
31		-	~~` {$ENDIF}`~~
	27	+	```text
	28	+	{$IFDEF MACOS}
	29	+	{$APPTYPE TOOL}
	30	+	{$ELSE}
	31	+	{$APPTYPE CONSOLE}
	32	+	{$ENDIF}
	33	+	```
32	34
33	35		... ensures it will be an MPW tool on Mac OS, and a console application in Delphi where {\$APPTYPE TOOL} is not recognized.
34	36
35	37		### Resources
36	38
37	39		Since 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.
38	40
39	41		### Error messages
40	42
41	43		Errors, warnings, hints and other messages written by the compiler are in MPW format - that is you can execute them and the error location will be displayed.
42	44
43	45		### Dos.Exec
44	46
45	47		The procedure Dos.Exec is used to execute other programs. In MacOS this is supported, and the program(s?) 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.
46	48
47	49		### Assembler symbols
48	50
49	51		Internal symbols in the generated assembler files will have a lowercase "s" as part separator instead of "\$". The reason is that PPCAsm does not support \$.
50	52
51	53		### QuickDraw globals
52	54
53	55		There is a variable qd defined in System.pp for use as the QuickDraw global.
54	56
55	57		For `{$APPTYE TOOL}` and `{$APPTYPE CONSOLE}` it is initialized, but for `{$APPTYPE GUI}` you have to initialize it yourself.
56	58
57	59		## Debugging
58	60
59	61		See [[MPW debugging]]
60	62
61	63		## Global variables
62	64
63	65		Currently all global variables are indirect, i.e. the entry in the TOC is always a pointer to data. (In the future small data items may be stored directly in the TOC)
64	66
65	67		Thus all references to globals are via a construct like: `lwz rX, yyy[TC](r2) ;loads a pointer to a global into rX`
66	68
67	69		## Cross compiling from Mac OS X to Mac OS
68	70
69	71		Although not necessary nowadays when there exists a native compiler for target MacOS, here is some info on how to cross compile. See also [[Link on target]].
70	72
71	73		### Crosscompiling step on macOS
72	74
73	75		When compiling, add these options:
74	76
75		-	~~` -Tmacos # target macos`\~~
76		-	~~` -st # do not generate executable, link on target`~~
	77	+	```text
	78	+	-Tmacos # target macos
	79	+	-st # do not generate executable, link on target
	80	+	```
77	81
78	82		If make is used, add `OPT=-st OS_TARGET=macos`
79	83
80	84		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 compiling any program, otherwise the search paths in the link script will not be correct.
81	85
82	86		You might also want to add option -a, then the link script will not delete unneeded 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.
83	87
84	88		### Assembling and linking step on Mac OS Classic
85	89
86	90		In case that host and target machine is different, transfer the produced files (assembler files (.s) and link script _ppas) to the host.
87	91
88	92		In Mac OS Classic, 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 not(?) obtain the proper mac file type, so this has to be fixed first e.g. with the MPW command SetFile.
89	93
90	94		Example: To build Hello World (together with the rtl unit system.pp), execute:
91	95
92		-	~~` Directory HD:Projekt:FreePascal:fpc:rtl:macos`\~~
93		-	~~` SetFile -c 'MPS ' -t 'TEXT' system_ppas`\~~
94		-	~~` system_ppas #executes the script`\~~
95		-	~~` Directory HD:Projekt:FreePascal:fpc:demo:text`\~~
96		-	~~` SetFile -c 'MPS ' -t 'TEXT' hello_ppas`\~~
97		-	~~` hello_ppas #executes the script`~~
	96	+	```text
	97	+	Directory HD:Projekt:FreePascal:fpc:rtl:macos
	98	+	SetFile -c 'MPS ' -t 'TEXT' system_ppas
	99	+	system_ppas #executes the script
	100	+	Directory HD:Projekt:FreePascal:fpc:demo:text
	101	+	SetFile -c 'MPS ' -t 'TEXT' hello_ppas
	102	+	hello_ppas #executes the script
	103	+	```
98	104
99	105		------------------------------------------------------------------------
100	106
101	107		Above circa 2004/5.
102	108
103	109		### Working notes: situation as of late 2012
104	110
105	111		The objective here is to build PPC and possibly 68K compilers, first as cross-compilers to run on a PC and then to run natively on Mac OS 9. 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.
106	112
107	113		On e.g. Debian Linux, build and install cross-binutils:
108	114
109		-	~~`tar xjf binutils-2.20.1.tar.bz2`\~~
110		-	~~`cd binutils-2.20.1`\~~
111		-	~~`./configure --prefix=/usr/local/powerpc-linux powerpc-linux-gnu`\~~
112		-	~~`make`\~~
113		-	~~`sudo make install`\~~
114		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/as /usr/local/bin/powerpc-linux-as`\~~
115		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/ld /usr/local/bin/powerpc-linux-ld`\~~
116		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/ar /usr/local/bin/powerpc-linux-ar`\~~
117		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/objdump /usr/local/bin/powerpc-linux-objdump`\~~
118		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/objcopy /usr/local/bin/powerpc-linux-objcopy`\~~
119		-	~~`sudo ln -s /usr/local/powerpc-linux/bin/strip /usr/local/bin/powerpc-linux-strip`\~~
120		-	~~`powerpc-linux-ld -V`~~
	115	+	```text
	116	+	tar xjf binutils-2.20.1.tar.bz2
	117	+	cd binutils-2.20.1
	118	+	./configure --prefix=/usr/local/powerpc-linux powerpc-linux-gnu
	119	+	make
	120	+	sudo make install
	121	+	sudo ln -s /usr/local/powerpc-linux/bin/as /usr/local/bin/powerpc-linux-as
	122	+	sudo ln -s /usr/local/powerpc-linux/bin/ld /usr/local/bin/powerpc-linux-ld
	123	+	sudo ln -s /usr/local/powerpc-linux/bin/ar /usr/local/bin/powerpc-linux-ar
	124	+	sudo ln -s /usr/local/powerpc-linux/bin/objdump /usr/local/bin/powerpc-linux-objdump
	125	+	sudo ln -s /usr/local/powerpc-linux/bin/objcopy /usr/local/bin/powerpc-linux-objcopy
	126	+	sudo ln -s /usr/local/powerpc-linux/bin/strip /usr/local/bin/powerpc-linux-strip
	127	+	powerpc-linux-ld -V
	128	+	```
121	129
122	130		Do the same for m68k-linux-gnu.
123	131
124	132		Build a cross-compiler to run on a PC but targeting PPC:
125	133
126		-	~~`cd /usr/local/src/fpc/fpc-trunk`\~~
127		-	~~`export PP=`\~~
128		-	~~`make "OPT=-O- -g" -C compiler powerpc`\~~
129		-	~~`mv compiler/ppcppc compiler/ppcXppc`~~
	134	+	```text
	135	+	cd /usr/local/src/fpc/fpc-trunk
	136	+	export PP=
	137	+	make "OPT=-O- -g" -C compiler powerpc
	138	+	mv compiler/ppcppc compiler/ppcXppc
	139	+	```
130	140
131	141		Renaming the compiler prevents it from being deleted by make clean etc., consider extending that OPT setting with -dEXTDEBUG.
132	142
133	143		Build a native RTL and compiler:
134	144
135		-	~~`export PP=/usr/local/src/fpc/fpc-trunk/compiler/ppcXppc`\~~
136		-	~~`make CPU_TARGET=powerpc OS_TARGET=macos "CROSSOPT=-st" rtl`\~~
137		-	~~`make CPU_TARGET=powerpc OS_TARGET=macos "CROSSOPT=-st" compiler`~~
	145	+	```text
	146	+	export PP=/usr/local/src/fpc/fpc-trunk/compiler/ppcXppc
	147	+	make CPU_TARGET=powerpc OS_TARGET=macos "CROSSOPT=-st" rtl
	148	+	make CPU_TARGET=powerpc OS_TARGET=macos "CROSSOPT=-st" compiler
	149	+	```
138	150
139	151		Bringing macos/sysdir.inc up to date shows that the amiga, embedded, watcom and symbian OS targets are similarly falling behind. It's instructive to compare the amiga target (which has not been updated) with the morphos target (which has).
140	152
141	153		There's also a problem inside the compiler itself where entries of type AT_NONE are being generated but not handled.
142	154
143	155		To be continued.
144	156
145	157		---
146	158		From the Free Pascal wiki, page "Target MacOS", as it stood on 2019-12-16 after a change by FTurtle, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).

Back to history