Lazarus Release 2.2.6

[pleumann]

Is there an official Ubuntu-on-ARM package for 2.2.6? I am currently moving my project around between my Mac running 2.2.6 and a Raspberry Pi (where it will ultimately be deployed) running 2.0.10 (because that's what's in the Raspberry Pi OS package sources). It does work, but there are a lot of pseudo-changes whenever Lazarus writes the version number into the form files. Also, there might be subtle differences in behavior that I am not aware of.

Cheers
Joerg

[JuhaManninen]

Is there an official Ubuntu-on-ARM package for 2.2.6?

No there isn't. It must be compiled either in Raspberry Pi itself or by cross-compiling.
Compiling Lazarus in native system using an installed FPC is very easy but may take some time in Raspberry Pi. I don't know how long. Those card computers are quite potent nowadays and have plenty of memory.
A long compilation time is not a problem when you do it seldom.

I recommend you skip Lazarus 2.2.6 and compile 3.0 instead. It has not been released yet but you can use fixes_3_0 branch which keeps getting bug fixes. Why compile an old version when you can compile a new one?

[pleumann]

Is there an official Ubuntu-on-ARM package for 2.2.6?

No there isn't. It must be compiled either in Raspberry Pi itself or by cross-compiling.
...
I recommend you skip Lazarus 2.2.6 and compile 3.0 instead. It has not been released yet but you can use fixes_3_0 branch which keeps getting bug fixes. Why compile an old version when you can compile a new one?

Thanks! I'll give building it on the Pi a try. It's not so much the compile time that scares me, but rather that for every weird problem I encounter using it I will ask myself if I did build it correctly.

I'll stick to 2.2.6, though. It's a company project, so I am a bit conservative.

Cheers!
Joerg

[TRon]

@JuhaManninen/pluemann
Building Lazarus on a pi is not a problem at all as I've been doing so starting with a 3b+. What is a problem however is the memory it requires with some pi's models having low specifications.

A build of fpc icw Lazarus requires a little over 1Gb (i have not tried latest release yet but expect it to be more memory hungry). The build can get very slow if you do not have such amount of (physical) memory because it requires you to increase the swap and when that is stored on a sd-card then things tend to slow down a little. Depending on the connected storage for the swap and/or amount of memory available on your pi you mileage may vary.

If you have a pi with 4/8GB of memory then you should have no problem and I would even advice to create a small ramdisk that you can use as storage media (though for 4gb it might be a bit close as a full install for both FPC and Lazarus requires around 1.5-1.8 GB).

[pleumann]

@JuhaManninen/pluemann
Building Lazarus on a pi is not a problem at all as I've been doing so starting with a 3b+. What is a problem however is the memory it requires with some pi's models having low specifications.

I use a Pi 400 with - I think - 4 GB for development, so I should be fine. Thanks for the hints!

I just built Lazarus on an Intel Mac, only to see if it works, and it was actually a no-brainer and completed in reasonable time for a project of this size. I am now downloading the source on an M1 MacBook to see if a native ARM version might have a noticeable performance advantage over the Intel version going through Rosetta2.

Cheers!
Joerg

[TRon]

I use a Pi 400 with - I think - 4 GB for development, so I should be fine.

A pi 400 indeed has 4gb out of the box (assuming you did not mod the hardware yourself)

Building Lazarus is indeed a no-brainer. It either builds or not and by doing a standard build you can't do anything wrong there. Do note that there are some dependencies that have to be met, for details see (generic linux) wiki (https://wiki.lazarus.freepascal.org/Installing_Lazarus_on_Linux) and there are some pointers for raspberry pi

I am now downloading the source on an M1 MacBook to see if a native ARM version might have a noticeable performance advantage over the Intel version going through Rosetta2.

In theory it should perform better but I also know that support for the new processors is not crystalized yet either so the actual answer might be a surprising one.

In case you wish to discuss more then please consider moving that discussion out of this (release) thread. Good luck !

[egsuh]

This is not limited to this version.

I have been installed with v2.2.4, and re-installed 2.2.6.
Some packages, especially weblaz, was installed in 2.2.4. Now, on 2.2.6, the fpweb pallette page is not displayed, while in packages>install/uninstall, weblaz is in the side of installed. The same thing happens to CEF3, and some others.
Hope you can check.

[CM630]

When I execute the already built exe outside the IDE the dialog is open properly.
I am not sure that I have succeeded to switch to GDB, so I have unchecked everything in Project options — Compiler options — Debugging. The open dialog kept stuck.
...

Like this, only gdb instead of fpdebug
https://wiki.lazarus.freepascal.org/Debugger_Setup

Or switch to Lazarus 3.0.RC1

Thanks, with GDB the Open dialog is really- really slow, but it does not hang.