│English (en) │ 한국어 (ko) │ русский (ru) │
This article applies to macOS only.
See also: Multiplatform Programming Guide
This list is aimed at to serve as a comprehensive repository of Pascal or OjectPascal compilers and interpreters: CDC 6000 Pascal compiler The source code for the first (CDC 6000) Pascal compiler. Delphi is Embarcadero's (formerly Borland/CodeGear) flagship rapid application development (RAD) product. It uses the Object Pascal language (termed 'Delphi' by Borland), descended from Pascal, to.
Note: For installation on Apple Silicon/AArch64, please refer to Apple Silicon Support.
Installing Lazarus on a Mac is not particularly difficult but it is critical that you do the install in the correct order. Skipping steps will almost certainly lead to tears. In brief, here is what you need to do:
These steps are explained in more detail below.
The detailed instructions assume a recent version of macOS on your Mac, a recent version of Xcode from Apple and a recent version of Lazarus. On the Legacy Information page, you will see older information that may be relevant if you are using older components. You can assist by replacing out of date info, either deleting it, or, if it may help someone working with a legacy project, moving it to the bottom of the page.
In general, this is about using both the Carbon and Cocoa Widget Set. While Carbon was once seen as a little more stable, with the release Lazarus 2.0.8 the 64 bit Cocoa Widget Set has now surpassed Carbon and should be considered seriously for any new projects. Carbon was intentionally (by Apple) limited to 32 bits and you should be aware that it has been removed completely from macOS 10.15 Catalina which only supports 64 bit Cocoa.
You need the Apple Developer tools, which are a part of the Xcode development environment.
Xcode 11.3.1 for use on macOS 10.14 Mojave must now be installed by downloading it from Apple Developer Connection (ADC), which requires free registration. Xcode 11.4.x for use on macOS 10.15 Catalina can be installed from the Mac App store. Note that you must first move any old Xcode versions from the Applications folder into the trash or rename the Xcode app (eg Xcode.app to Xcode_1014.app). You can select which version of Xcode to use with the command line utility xcode-select.
The developer tools can be installed from the original macOS installation disks or a newer copy downloaded from the Apple Developer Connection (ADC), which requires free registration. Download the Xcode file, it will end up in your Downloads directory as a zip file. Click it. It is unarchived into your Downloads directory. You may be happy with it there but maybe not. Other users will see the path to it but be unable to use it. And it is untidy there. So I moved mine and then told xcode-select where it was moved to (in a terminal) -
This is shown here as a separate step because it really is a separate step in addition to Step 1. Don't confuse this with the internal Xcode command line tools that the Xcode GUI will tell you are already installed. Lazarus cannot use those Xcode internal command line tools, so do the following (it is quick and easy)-
If you have problems installing using this command line method (e.g. the installer freezes while 'finding Software'), you can also download and install the package by logging in to the Apple Developer Site and downloading and installing the Command Line Tools for Xcode Disk image.
Download and install the Free Pascal Compiler (FPC) binaries and the separate source package. A compatible FPC (and source) must be installed before you install Lazarus. You have a number of options.
Download the Free Pascal Compiler (FPC) binaries and FPC source packages from the Lazarus IDE file area. When you arrive at that file area, choose the correct version of your operating system. The vast majority of Mac users should now choose the 64 bit packages in the Lazarus macOS x86-64 directory. Every Mac computer since late 2006 has been 64 bit capable. The fact that Apple has completely dropped all 32 bit support from macOS 10.15 Catalina (released in October 2019) is another reason to choose the 64 bit packages.
These binary install kits are built by the FPC/Lazarus developers and track formal releases. As these install kits are not approved by Apple, you need to hold down the Control key, click the package and choose Open and confirm you want to install from an Unknown Developer.
You might like to apply a simple and quick test of FPC at this stage - Testing FPC installation.
You could also consider using fpcupdeluxe to install FPC and, perhaps Lazarus.
Alternatively, you can use fink, a package manager for macOS to install FPC. Note at the time of writing (Early 2020) fink offers Lazarus 2.0.6. The extra bonus of fink is easy installation as well as clean removal of a huge number of other open source software packages, including Free Pascal crosscompilers for many processors and systems. The choice for Lazarus is between a Carbon or Cocoa look, a gtk2 look, a Qt4-based and a Qt5-based version:
You will be asked, whether to install a number of dependencies, including the Free Pascal Compiler, the Lazarus sources. Simply hit RETURN at the prompt and go for a coffee. It may take quite some time to build all packages, in particular on older Macs.
After installation, Lazarus can be started from the folder /Applications/Fink/. The actual details of FPC and Lazarus are in subdirectories of /sw
With any Lazarus package from fink, these widget sets are supported for your program on macOS:
carbon (Aqua), cocoa, gtk2, qt4 (Aqua), qt5 (Aqua), nogui, win32, win64 and wince.
If you install FPC from fink, you will be fine downloading Lazarus source and compiling as detailed below. However, its possibly not a good idea to mix fink FPC with the Sourceforge binary install of Lazarus.
MacPorts has also a package description of the cocoa-64 bit version of lazarus 2.0.6. Install it with:
Download and install the Lazarus IDE from the Lazarus IDE file area. When you arrive at that file area, choose the correct version of your operating system. The vast majority of Mac users should now choose the 64 bit packages in the Lazarus macOS x86-64 directory. Every Mac computer since late 2006 has been 64 bit capable. The fact that Apple has completely dropped all 32 bit support from macOS 10.15 Catalina (released in October 2019) is another reason to choose the 64 bit packages.
In versions of Lazarus 1.8.4 and earlier, you needed to use gdb as a debugger, slow to install and hard to sign. Since Lazarus 2.0.0 you can (and should) use lldb, a debugger provided by Apple, no signing required.
Assuming you have installed what is necessary and started Lazarus, all that remains is configuring the debugger. If you don't do this now, Lazarus will try to use gdb and fail.
First, click Tools > Options > Debugger. Top right of the window now open has a label, 'Debugger type and path', you must set both. Select 'LLDB debugger (with fpdebug) (Beta)'.
If it is not shown in the selection list, see Installing LazDebuggerFpLLdb below. The XCode command line tools install lldb to the /usr/bin directory. Save those settings and you can now try to compile the almost nothing program that Lazarus has kindly provided for you (click the small green triangle near top left).
Next you see a puzzling question, see image below. Choose a 'Debug Format' from one of the offered -
Martin_fr, the person who has given us this interface between Lazarus and lldb, suggests you use 'dwarf3' . Then, you need to enter your password, a macOS cuteness because one application appears to be interfering with another. In this case, that's fine!
When running the debugger from time to time you will be asked for your password to allow debugging. This is for your own safety.
A great deal of information about using lldb appears in this forum thread. Here are a few gems, again, from Martin_fr:
In the unexpected case of problems, it may be worth trying 'dwarf with sets' instead of just 'dwarf3'.
The 'debug info' setting only affects the units directly in your project. However, units in packages may have debug info too. This can be:
If you change settings for a package, you might want to check which package you expect to step into when debugging. Packages you do not step into, do not need debug info.
If you use a type from a package (such as TForm from LCL) it is enough that your unit (in which you declare the variable / must declare and use a variable to include the type) has debug info. Reducing the number of packages with debug info (including those that default to have debug info), can shorten the debuggers start-up time.
Also it may be worth comparing (it has not been tested) the debuggers start up time for the same settings, only changing the checkbox 'use external debug info'.
This needs to be only set in your project. If set in your project it will affect all packages. (If set in a package it will do nothing / at least should...)
If you installed from source and used the bigide parameter to make, then the correct debugger will be installed, as a package, and ready to go. If, however, you installed in another way, it may, or may not be there. From the main IDE screen, click Packages->Install/UninstallPackages. Shown is two lists of packages, the list on the left is installed, the list on the right is available to install. Look for LazDebuggerFpLldb (exactly that, there are some similar named but less suitable packages). If it is on the right hand side, click it, press 'Install Selection' and then 'Save and rebuild IDE'. This will take a little time, the IDE will shutdown and restart and all should be well. Now jump back up the page and continue configuring the debugger.
Lazarus using the Apple 64 bit Cocoa framework should now meet the needs of users. The Apple 32 bit Carbon framework works pretty much as expected but you are advised to try Cocoa first, because Apple has dropped support for 32 bit applications and the Carbon framework from macOS 10.15 Catalina which was released in October 2019.
Alternatives include QT and GTK2+, both requiring additional libraries and GTK2+ on the Mac appears to get little attention these days. QT on the Mac does have some strong supporters on the Lazarus forum.
Cocoa is now undeniably the future on the Mac. It is possible to build an all Cocoa version of Lazarus with release 2.0.0 and later. It is also possible to make a Carbon install of Lazarus (unless you are running macOS 10.15 Catalina or later) and use that to generate Cocoa 64 bit binaries.
In the Carbon or Cocoa IDE, you need to set the Target to the 64 bit processor and select the Cocoa Widget set:
Not every combination of Lazarus and Free Pascal is compatible with every installation of macOS. Please refer to the following table in order to find the correct version for your development environment:
|Lazarus 1.6.0||Lazarus 1.6.2||Lazarus 1.6.4||Lazarus 1.8.x||Lazarus 2.0.y||Lazarus 2.0.8||Lazarus 2.0.10|
|FPC 3.0.0||FPC 3.0.2||FPC 3.0.4||FPC 3.2.0|
|Mac OS X 10.4 (Tiger)||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible|
|Mac OS X 10.5 (Leopard)||Not tested||Not tested||Not tested||Not tested||Incompatible||Incompatible||Incompatible|
|Mac OS X 10.4 (Tiger)||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible||Incompatible|
|Mac OS X 10.5 (Leopard)||Not tested||Not tested||Not tested||Not tested||Compatible^||Not tested||Compatible^**†|
|Mac OS X 10.6 (Snow Leopard)||Compatible||Compatible||Compatible||Compatible||Compatible*||Not tested||Not tested|
|Mac OS X 10.7 (Lion)||Compatible||Compatible||Compatible||Compatible||Not tested||Not tested||Not tested|
|OS X 10.8 (Mountain Lion)||Compatible*||Compatible*||Compatible*||Compatible*||Compatible||Compatible**#||Compatible**#|
|OS X 10.9 (Mavericks)||Compatible*||Compatible*||Compatible*||Compatible*||Compatible||Compatible**†||Compatible**†|
|OS X 10.10 (Yosemite)||Compatible*||Compatible*||Compatible*||Compatible*||Compatible||Compatible**†||Compatible**†|
|OS X 10.11 (El Capitan)||Compatible*||Compatible*||Compatible*||Compatible*||Compatible||Compatible***†||Compatible†|
|macOS 10.12 (Sierra)||Compatible*||Compatible*||Compatible*||Compatible*||Compatible||Compatible***†||Compatible†|
|macOS 10.13 (High Sierra)||Not tested||Not tested||Compatible||Not tested||Compatible||Compatible***†||Compatible†|
|macOS 10.14 (Mojave)||Not tested||Not tested||Not tested||Not tested||Compatible||Compatible***†||Compatible†|
|macOS 10.15 (Catalina)||Not tested||Not tested||Not tested||Not tested||Compatible||Compatible***†||Compatible†|
|macOS 11.0 (Big Sur Dev Beta 6)||Not tested||Not tested||Not tested||Not tested||Compatible||Compatible***†||Compatible†|
^ Carbon interface compiles - Cocoa does not.
* Restrictions apply to debugging with gdb.
** See Installing Lazarus 2.0.8, 2.0.10 with FPC 3.2.0 for macOS 10.10 and earlier for instructions.
*** See Installing Lazarus 2.0.8 with FPC 3.2.0 for macOS 10.11+ for instructions.
# Cannot run with/without debugging in the IDE. Can run compiled application outside of the IDE. See Issue #37324
† Cannot run without debugging in the IDE. Can run compiled application outside of the IDE. See Lazarus IDE - Unable to 'run without debugging' for workaround. See Issue #36780.
x = 0, 2 or 4; y = 0, 2, 4, 6, 8 or 10
There are a number of reasons why you may be better off using a non-release version of Lazarus, specifically, fixes_2_0. Particularly:
Precompiled binaries based on fixes_2_0 are not available from SourceForge but can be obtained from fpcupdeluxe. But here we will discuss downloading source and building. A little slow initially but very reliable and a great test of your compiler install ! You will need git which is included in all recent versions of the Xcode command line tools which you should have already installed (see Xcode Command Line Tools above).
About svn or git: The XCode 11.4 command line tools on macOS 10.15 no longer install svn, only git. You can install subversion via fink, ports or brew.
Create a directory for Lazarus and download the current fixes version:
Depending on your internet connection and server congestion this takes a few seconds or a couple of minutes. Then build it:
You might like to put a small script in your $HOME/bin directory and even set a path to it (very UNIX!)
To keep your fixes_2_0 installation up to date is as easy as:
Precompiled binaries based on trunk are not available from SourceForge, so here's how to download the trunk source using git and build the Lazarus IDE. You will need git which is included in all recent versions of the Xcode command line tools which you should have already installed (see Xcode Command Line Tools above).
To update your existing trunk source.
The bigidemake argument adds a bunch of packages to Lazarus that many find useful and accent dow without. The packages that are added are:
The above list is sourced from the [Lazarus source directory]/IDE/Makefile.fpc and may be subject to change.
Note that if you have not compiled your own Lazarus IDE with the bigide argument, you can install any of these packages yourself using the Lazarus IDE Package > Install/Uninstall Packages... dialog.
Note that since fpc trunk is by definition still under development, some of the features may still change before they end up in a release version.
The source code is kept in a version control system called subversion or svn for short, and is mirrored in git:
Create a directory where you would like to put the source (eg fpc in your home directory). You don't need to be root to do this. Any normal user can do this. Open an Applications > Utilities > Terminal and do the following:
This will create a directory called 'fpc', which can be later used in the IDE, and download the FPC source to it.
To subsequently download/update the latest source changes you can simply do:
To build and install FPC (the highlighted text should be all on one line):
You will also need to update the links for the compiler in /usr/local/bin which will be pointing to the previous FPC version. For example:
Note that you will need to build a new
ppc386 compiler if you want to continue to compile 32 bit applications by replacing these lines (this may not be possible after Xcode 11.3.1 and macOS 10.14.6 Mojave because of Apple's removal of 32 bit frameworks):
with these two lines:
Now rebuild Lazarus with this build_laz.sh shell script (adjust path for Lazarus source as required):
Note: The highlighted line above should all be on one line.
Note: The highlighted line above should all be on one line.
You should now be able to successfully compile and run the Lazarus default blank form project.
Now follow the steps above.
If you are using the Lazarus IDE 2.0.10 and the Run > Run without debugging menu option fails with a dialog similar to:
then you need to patch the Lazarus 2.0.10 source code (Issue #37324 and Issue #36780). Specifically, patch ../ide/main.pp as below (unpatched lines shown first, patched lines shown second):
and recompile the Lazarus IDE.
Alternatively, you can omit patching the source code and simply recompile Lazarus 2.0.10 with FPC 3.0.4.
A similar patching exercise and recompiling, or simply recompiling with FPC 3.0.4, needs to be done for Lazarus 2.0.8 if it has been compiled with FPC 3.2.0.
sudo xcode-select --install
on the make command line because FPC ignores the /etc/fpc.cfg configuration file during builds of itself.
The complete uninstall of all fpc and lazarus packages is done with:
If you want to preserve changes to the preference file /sw/etc/fpc.cfg, do:
For the removal of the Lazarus preferences subdirectory in your home directory, and the files that it contains, see the end of the next section.
Normally you uninstall an application on macOS simply by dragging it from the Applications folder to the trash. But because Lazarus and Free Pascal are development tools, they're installed in several folders that you don't normally see in Finder.
You can copy and save the commands below to file uninstallLaz.sh and run it if you need to uninstall Lazarus and Free Pascal. You can usually install newer versions of Lazarus and Free Pascal over older versions, but as with most software it's not a bad idea to clean out everything before you install a newer version. This list of commands should also give you a sense of where the various pieces of Lazarus and Free Pascal are located.
Note that this assumes you have version 3.0.4 of Free Pascal installed. If you have a different version, change the two lines with a version number to specify your version.
To run this script, change to the directory where it's stored and enter:
Then enter your password when prompted.
Lazarus preference folder .lazarus in the home directory
Lazarus also creates a .lazarus preferences subdirectory in your home directory where it stores environment settings and a list of recently opened projects and files. You can leave this folder alone if you want the new version of Lazarus you're installing to use your old settings. macOS normally doesn't show files or folders whose names start with a dot (.). To see this folder and its contents, open an Applications > Utilities > Terminal and enter the following in the Terminal window:
To remove it, execute the following commands: