Die Lazarus Expedition Mac OS

This article applies to macOS only.

• Die Lazarus Expedition Mac Os X
• Did Lazarus Die
• Die Lazarus Expedition Mac Os Catalina

See also: Multiplatform Programming Guide

• Xcode 3.1.x compatibility (Mac OS X 10.5) Most versions of Lazarus and FPC are compatible with Xcode 3.1 (see the compatibility matrix for detailed reference). The Xcode integration kit is provided as an optional install to allow for developing with Free Pascal directly from Xcode. It is not required for development with Lazarus, however.
• #1) I do have the Lazarus Form Recovery extension. It no longer works and hasn't worked for a very long time. You won't be able to make it work, unless you're stll using OS X 10.8. It broke with 10.9 (Mavericks,) which came out in October of 2013. #2) I'm not sending the lfr.safarietz file to you. I might consider it, if you'd apologize.

│English (en) │

• 4Installation - PowerPC-based Macs
• 6Xcode Compatability

Pre-built Lazarus install works, it's only when I try to rebuild it there are issues. However, I need to be able to rebuild in order to install design-time packages. Setup: - Late-2012 model Mac Mini - Mac OS X High Sierra (the machine was reformatted with Sierra installed, then upgraded from there via App Store) - XCode 9.2 - Lazarus 1.8.0. Lazarus is a free cross-platform visual integrated development environment (IDE) for rapid application development (RAD) using the Free Pascal compiler. Its goal is to provide an easy-to-use development environment for programmers developing with the Object Pascal language, which is as close as possible to Delphi. Software developers use Lazarus to create native-code console and graphical.

Compatibility

Not every combination of Lazarus and Free Pascal is compatible with every installation of the Mac operating system. Please refer to the following table in order to find the correct version for your development environment:

* Restrictions apply to debugging with GDB.

** Not available as pre-built installer. Compiling from source required.

FPC 2.4.4 bug

• FPC 2.4.4 has a bug. You can not compile the IDE with the range check flag -Cr.

Mac OS X 10.4 Tiger

• On Mac OS X 10.4 Tiger you have to manually uninstall any previous version before installing a new dmg. Delete the following files and folders:
  • /Developer/lazarus
  • /Library/Receipts/lazarus.pkg
  • /etc/lazarus
  • /usr/local/bin/lazbuild

Installation - PowerPC-based Macs

Download the three disk images (.dmg files) for fpc, fpcsrc and lazarus from the following link:

Open up each disk image and install in this order:

1. fpc
2. fpcsrc
3. Lazarus

After installation the Lazarus application can be found in /Developer/lazarus/, the FPC source files in /usr/local/share/fpcsrc.

If you receive a 'Can't find unit Interfaces used by Project1' error on trying to compile a blank form, check the following settings in Lazarus (should be set by default):

Environment Options

Project | Options

Project | Inspector

Note - different versions of Lazarus depend on particular versions of the Free Pascal compiler and will not work with other versions.

Another common problem is that the versions of fpc and fpcsrc are different.

Download stable sources

The source code of stable versions is available in the Lazarus Zip - GZip archives. This is an option for users, who want to run the latest official Lazarus versions on 'unsupported' machines, e.g. PPC-based Macs. Provided that you have installed the latest stable FPC version together with sources, it is sufficient to download and unpack the zip archive. Move it to the desired location (e.g. your /Developer folder), open a terminal window and change the shell's path to this folder (the easiest way to do this is to type 'cd ' and then to drag the icon of the freshly unpacked Lazarus folder to the position after this command in the Terminal window). If necessary enter and then

and again. Subsequently, FreePascal will use the makefile in this folder to build the Lazarus IDE. This may take a few minutes, but the process is fully automated. Therefore, you might want to look for a cup of coffee, while FPC is working. If the compiler is ready it prints the number of processed lines and the required time to the shell's output.

The last step is to right-klick on the Lazarus bundle icon and to select 'Show Package Contents' from the context menu. Then drag the executable 'lazarus' to the folder 'Contents/MacOS' of the bundle. That's it.

Installing gdb

As of the Lazarus 2.0.0 release this is entirely optional. The IDE now supports LLDB directly. See http://forum.lazarus-ide.org/index.php/topic,42869.0.html and http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes#LLDB_based_Debugger_.28New.29

Getting gdb to run can be a bit tedious but is worthwhile in the end if using Lazarus < V2.0 or have some specific requirement for gdb. You probably don't !

This step should be done after installing XCode and before installing FPC/Lazarus.

1. Install fink or brew and use them to install gdb- http://wiki.freepascal.org/GDB_on_OS_X_Mavericks_and_Xcode_5
2. Self sign the gdb binary using tools already on your Mac - https://sourceware.org/gdb/wiki/BuildingOnDarwin This is the tedious part. The instructions are clear except, perhaps they could have mentioned that after you have set the Keychain to 'System' you need click ‘Create' and ‘Done' on the next screen. Then go and find the cert in your overall list of certs to do the next instruction 'using the contextual menu…'. Don't worry about step '2.1.4 Disable starting the debuggee…', we'll address that once Lazarus itself is installed and working.
3. Once Lazarus is installed and fired up, tell it how it should start gdb, that is step 5.

Note that as of April 2018, there may be issues with newest gdb and High Sierra. https://forum.lazarus.freepascal.org/index.php/topic,40874.0.htmlAccording to https://stackoverflow.com/questions/49001329/gdb-doesnt-work-on-macos-high-sierra-10-13-3, gdb 8.1 does not work on High Sierra, but 8.0.1 does.

Part 2 of gdb install, Tell Lazarus about starting gdb

Again, this step is not necessary with Lazarus V2.0 and later. See http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes#LLDB_based_Debugger_.28New.29 If you do install (and use) gdb, you must tell Lazarus about how to call gdb. Obviously, this step happens after Lazarus is installed.

OK, now you should be able to start Lazarus, it should display the various parts and paths it needs (including gdb) in the little opening screen. You will get an alert there if you chose to not use a debugger. Proceed to the IDE and we now need to tell Lazarus to tell gdb to not open a shell, as noted by a number of Forum users (http://forum.lazarus.freepascal.org/index.php/topic,37310.0.html). Within Lazarus, click Tools > Options > Debugger > GeneralIn the 'Debugger specific Options' there is a field labeled Debugger_Startup_Options. Type in '--eval-command=set startup-with-shell off' (including the inverted commas) AND press the return key, click OK. Note you cannot copy and paste into this box (##$!). See screen shot.

Xcode Compatability

Information relating to older versions of FPC, Lazarus and Apple Developer Tools

Compatibility with Xcode 5.0 and newer versions (OS X 10.8, 10.9, 10.10 and 10.11)

Like Xcode 4.3+, Xcode 5 and subsequent versions no longer install the command line tools by default. These are required by FPC/Lazarus, however. Unlike in Xcode 4, the installation option is no longer accessible in Xcode 5 via the Downloads tab. Additionally, the 'Locations' tab of the preferences dialog may be confusing, as it mentions that the command line tools are installed:

• Default location of command line tools in Xcode 5.

• Installation of command line tools with the xcode-select command part 1..

• ..and part 2.

The first dialog box shows that by default the command line tools are only installed inside the Xcode.app bundle itself. To install them globally, as required by FPC/Lazarus, execute the following terminal command:

Depending from your Xcode version alternative steps to install the command line developer tools may be to download them directly in the Xcode preferences window (see screenshots above) or to download them from developer.apple.com (please take care to install the command line tools that are correct exactly for your Xcode version).

• You can compile and install the normal gdb. See GDB on OS X Mavericks and Xcode 5.

Xcode 4.3+ compatibility (Mac OS X 10.7 / OS X 10.8)

Xcode 4.3 and later no longer install the command line tools by default. These are required by FPC/Lazarus.

To install them manually, open Xcode, go to Preferences, select 'Downloads;' and install the 'Command Line Tools'. Afterwards, FPC will install and function correctly.

It will be necessary to reinstall the command line tools after each upgrade of Xcode (especially when it's a new major version, the installer may delete the old copies of the command line tools), and also after switching to a new major version of the system software (idem). You may also download the command line tools from Apple Developer.

Xcode 3.2.x compatibility (Mac OS X 10.6)

FPC 2.6.0: there is an issue when compiling dynamic libraries with FPC under Mac OS X 10.6 due to a bug in the Xcode 3.2.x linker. This bug has been fixed in Xcode 4. You can work around the bug in Xcode 3.2.x by using the -k-no_order_inits command line parameter when compiling a dynamic library.

Xcode 3.1.x compatibility (Mac OS X 10.5)

Die Lazarus Expedition Mac Os X

Most versions of Lazarus and FPC are compatible with Xcode 3.1 (see the compatibility matrix for detailed reference). The Xcode integration kit is provided as an optional install to allow for developing with Free Pascal directly from Xcode. It is not required for development with Lazarus, however.

Xcode 2.x compatibility (Mac OS X 10.4)

Most versions of Lazarus and FPC are compatible with Xcode 2.3 or newer (see the compatibility matrix for detailed reference). The Xcode integration kit is provided as an optional install to allow for developing with Free Pascal directly from Xcode. It is not required for development with Lazarus, however. Xcode 2.0 was compatible with Lazarus 0.9.x, but it is no longer supported by newer versions of the Lazarus IDE.

Made and Published by Maschinen-Mensch

Played on: Microsoft Windows

Also Available on: MAC OS and Linux

We all know the many famous explorers that have graced our history textbooks. Greats such as Charles Darwin, Amelia Earhart, H.P. Lovecraft, Marcus Garvey.? Okay, some of these great people may not be explorers, but they are famous, and have had an impact on the world in one way or another. The Curious Expedition is a rogue-like, turn based strategy game with procedurally generated maps. The friendly old ghost mac os. The goal is to compete against four other explorers and have your explorer, whom you pick, become the most famous of them all. You will have to travel to Africa, Asia, Australia, South America, Antarctica and many other places in your search for treasure.

When playing the game, you will have six expeditions. Each one will become progressively harder. The final goal of each expedition is to find the golden pyramid, located somewhere on the map. The maps slowly get larger, and many obstacles will stand in your way. The first three expeditions simply require you to find the golden pyramid. The final three expeditions will have you wander the map looking for moonstones. You will need one or two of these stones to be able to gain entry into the golden pyramid.

With the map changing every time due to you being able to pick the area you explore in addition to the procedural generation, the game never feels old. Every expedition will feel new and exciting. You will encounter villages with indigenous peoples, sacred temples, abandoned campsites and shipwrecks, mysterious caves, and an assortment of other locations to explore and loot. Exploration in the game is done in a turn-based manner. You will click the place you want your exploration party to go to on the grid based map and they will move to that location. They can go as far as you want them to in one turn, as long as the place they are going was revealed to you on the map before you sent them and they are not interrupted along the way. Moving consumes sanity, which is important. Sanity is what keeps your party together. Moving through rough environments such as thick jungles and deep rivers will drain your party of sanity. If you run out of sanity, increasing bad things will happen to your band of explorers, and they will eventually perish from the game's pixelated Earth. In addition to exploring the map, you will have to face it's many dangers. Ravenous wildlife roam the land, and are alerted to your presence whenever you stop to rest or loot an important location. If you desecrate too many sacred sites, the native people will send out armed search parties to hunt you down and sacrifice you to their gods.

Did Lazarus Die

Combat in the game is straightforward. You and your party members will face the enemy in turn-based combat, similar to many JRPG games. The difference here is that each character in your party will have a different set of die that can be rolled any number of times depending on how many people are in your expedition (i.e. if you have five people, the maximum, you can roll your die five times before your turn ends.) Some characters only have support die while others only have attack die. You mix and match these different skills to make powerful and/or helpful attacks and defensive abilities in battle. But be careful, like in many turn-based games, if the main character dies in battle, (your explorer), then the game ends.

If you make it to the golden pyramid, you will return to London. There, you will first get to pick an upgrade. You are presented with three random upgrades after each expedition. Some of these increase the amount of sanity you have. Others will make you lose less sanity when crossing certain terrain, or allow you to carry more items among others. Afterwards, you will sell off the treasure you have found. You can either sell your treasure to the museum, and get fame, which if you have the most fame you win, or, you could sell your treasure on the open market to get cash for your next expedition. Finally before you depart, you will get a chance to buy new equipment, upgrade some of your party members, and get a quest opportunity which you can or cannot accept. These quests tend to repeat each playthrough and consist of finding a person or delivering a letter to someone. If you complete the quests while on your next expedition, then you will receive a cash benefit or a small amount of fame. If you fail, then you will have fame deducted from your total score and not get any money.

While I really like the game for it's variety and personal charm, I have issues with it. My first is the game's performance issues. On my computer (which can run the game perfectly fine according to the system specs on the steam page) I have encountered many glitches that really ruin the experience. The first one I noticed is the sound. The soundtrack to the game is very fitting for exploration in the game's engrossing world and I really enjoy listening to it while playing the game. However, it sounds like a small mammal being run through the garbage disposal at times. I would be investigating a tomb in sub-saharan Africa, and then all of the sudden hear the slow, distorted lurching of the rhyme to the main theme. It really does sound awful and I turn the volume off every time it happens, which is pretty frequent. Other performance issues include the frame-rate dropping and the combat screen taking a while to appear. These didn't happen to me often but they are still a persistent problem.

Die Lazarus Expedition Mac Os Catalina

Another issue I have with the game is the autosave feature. Every few minutes the game will auto-save due to the lack of a manual save function during expeditions. While this did help a few times after I died and wanted one last shot at completing the expedition, this feature is mostly there to taunt you. Most of the time the game saves right before you are ambushed by an enraged group of natives or before you party suffers from a third night without any remaining sanity. I'm not even sure why the game has an autosave feature. From my experience it really only seems to give you the ability to see the moment of your demise over and over again. Frankly I think sticking with the permadeath one-and-done gameplay would have been a better option.

Overall, The Curious Expedition is a pleasant experience. It has hours of the reliably fun permadeath, roguelike gameplay that we see in other great indie games like The Binding of Isaac and Organ Trail. The maps are full of entertaining stops and objectives that tie into the overall goal of the game. The combat takes a different approach from other games, which is a good thing as this keeps the game feeling new in a crowded genre. I think that the game is worth 15 dollars despite the performance issues. They may make the game less satisfying to play, but really don't get in the way of the enjoyment. Just don't wear headphones. As always, a VITA version of this game would be epic, and would help eliminate performance issues, but I know that we won't be seeing any of that, at least not soon.

I am giving The Curious Expedition an 8 out of 10

Pros:

Fun concept and execution

Great turn-based combat

Procedural generation mixed with turn-based movement done well

Cons:

Minor performance issues

Annoying auto save system

Where to buy: