I'm in the same boat, having just upgraded to Catalina.1) You can put it anywhere.
I've downloaded the SDKs, specifically the one for High Sierra, but now haven't got a clue what to do with it. The instructions are rather vague as to where to put this, and how to get Lazarus to see it (along with the 64 bit ones).
That simple?Sorry, I never use Lazarus for compiling, only for editing and code navigation.
Well, for me, not so. Where does one put the -XR/<path>?
After a bit of Internet searching, all I could find suggested addingI can't help you with this, but please never use "' -k-macosx_version_min -k10.5'". Use -WM10.5 instead.
if TargetOS = 'darwin' then begin UsageCustomOptions += ' -k-macosx_version_min -k10.5'; UsageCustomOptions += ' -XR/Library/Developer/CommandLineTools/SDKs/MacOSX10.13.sdk/'; end;
To Project Options->Custom Options, in the top box with macOS 32bit Build mode selected (which worked OK before I upgraded). I even tried in the bottom box with no luck. I also tried adding -XR/<path> to the end of the Compiler executable entry in Tools->Options->Environment->Files, but it didn't like the entry when I clicked on OK.
Try adding it directly in the custom options box, i.e. just add your -XR parameter there without any if-check, quotes, or "UsageCustomOptions +=".Yep, that did it. Thank you.
The only Mac computer in the last 15 years that could not run 64 bit applications was the 2006 Mac mini with Intel Core Solo processor. Do you really need to compile 32 bit applications?That was what I was wondering, if it was all worth the effort.
1) install a Virtual Machine of Mojave using either Parallels ($$) or VMware Fusion ($$ / free for personal use);Tried that - took bloody ages and didn't get me anywhere, so I gave up when I found the other solution. I was also starting down the path of installing Lazarus onto our MacBook Air, running High Sierra.