I know Lazarus itself installs like magic under Win7. I also know Lazarus installation under Mac is a nightmare and, to this date, I can get it to install ... but not compile ... (Before High Sierra I couldn't get it to install. Under High Sierra I can now get the IDE to come up and appear to run -- but then choke when I try to compile.)
Vague. Maybe you didn't install the Xcode command line tools?
Both FPC and Lazarus are pretty straightforward to install and run on macOS. The debugger is tricky since Lazarus uses gdb, which is not the debugger on macOS, so gdb has to be installed from 3rd party. However, you can compile and run in Lazarus without the debugger, then debug as needed from the command line using the Xcode lldb debugger.
The problem that Lazarus faces at the moment on macOS is that it's currently a 32-bit app and macOS is going to be 64-bit only pretty soon.
--
No, actually I did. I picked to upgrade to 10.13.3 *specifically* in the hope I might get Laz to install. I think it was I had tried for hours to get a previous version of Lazarus to install and run under Sierra (I avoided trying earlier versions of Sierra because, as I recall, there was quite a mess with it "not being ready for prime time"/ security, etc.
As I recall, I noticed homebrew/cask/lazarus and entrusted the install to brew. It, in turn (it is generally wonderful in this regard, which I why I am suggesting we work closely WITH the leading software install/upgrade managers under the various platforms) took care of identifying my need to update Xcode. And it identified the need for GDB and took care of that, too, if I recall (or possibly I started with using brew to install GDB or Xcode first...it is lost in the history of time and complexity and becoming "the tool of my tools", I confess.
Anyway, the install went like magic compared to earlier attempts to get Lazarus running under an earlier version of MacOS. After that and when homebrew was done I tried Lazarus, with a lot of trepidation and not really expecting it to work.
I was kind of ecstatic when it came up to the IDE perfectly. And I thought "happy days!" And so I started typing in a super simple IDE based program through the form designer. And that went well.
And then I tried to compile and it crapped out with multiple error messages pointing to graphics incompatibilities (cocoa oriented if I recall). And THAT was where I found out Apple had changed graphics support...and Lazarus specifically said it cut off MacOs support at 10.12.
And I posted for any help here. And I got one lead but it was over my head.
And I gave up.
What I don't think most "modern" software developers realize is that there was a day when software JUST WORKED. It might have a bug, but most of the bugs were not fatal and could be worked around. Borland aka Turbo Pascal was one of the leaders of the JUST WORK movement -- actually Borland software went way beyond "just work" which is why they were able to steal Microsoft's thunder.
But Microsoft was a sneaky bastard of a competitor...and Apple and Google and eventually pretty near everyone else (specifically Google) adopted their playbook of stacking complexity upon complexity and "upgrade" hell. That is how they came to own us. Well, most of us! Lazarus team is obviously like Neo or maybe Luke in the unfolding plot. Or so I hope! :-)
Anyway, I can get you specific error codes if that would help. Or I can just bide my time until, hopefully, the Lazarus development team gets around to adapting to Apple's upgrade path? Whatever you suggest. It would be nice to have my Mac Air working with Lazarus as that would dramatically increase my exposure to the IDE learning curve ... which in the longer run would probably increase my investment of time and eventually money in Lazarus.
Or I can wait, as my real plan is to shift my business to Linux out of Windows (I'll go wherever you think Laz + SQLite/Postgres is best supported and strategic, I expect).