Forum > Lazarus
Lazarus Release 2.2.2
mattias:
The Lazarus team is glad to announce the release of Lazarus 2.2.2.
This is a bugfix release and was built with FPC 3.2.2.
Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.2.2
Here is the list of fixes for Lazarus 2.2.x:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_2_2
The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/
Choose your CPU, OS, distro and then the "Lazarus 2.2.2" directory.
Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_2_2
Minimum requirements:
Windows:
2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.
FreeBSD/Linux:
gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.
Mac OS X:
Cocoa (64bit) 10.12 to 12.3, Carbon (32bit) 10.5 to 10.14, qt and qt5 (32 or 64bit).
The gitlab page:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_2_2_2
For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:ftp://ftp.freepascal.org/pub/lazarus/releases/
loaded:
Many thanks to the lazarus developers. :)
Zvoni:
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?
And many thx to the Lazarus-Devs
Martin_fr:
--- Quote from: Zvoni on May 19, 2022, 10:20:06 am ---Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?
--- End quote ---
Not sure where/when this recommendation came to be....
But I am using the 64 bit version.
[[EDIT: I am using fpc 3.2.3]]
And I would recommend, if you have a 64 bit PC and a 64bit Windows:
- If you compile all your projects to 32 bit, and 32 bit only: Use the 32bit IDE (just to save installing the cross compiler / the 64bit + cross32 will work just as fine)
- If you need the WinCe-arm - use the 32bit IDE.
- In all other cases use the 64bit IDE
>>EDIT:
Or maybe this was with regards to the 64bit fpc version 3.2.2
FPC 3.2.2 has several bugs that affect the generated code. Meaning the compiled project will end up with a bug.
They only occur in very rare situations.
One of this bugs has only been observed on Win64.
"observed" => i.e., it may well exist on other targets, it is just not known.
IIRC, in the meantime I heard about a 2nd such issue, that afaik was observed on Linux (not sure of the bitness).
At least the one bug that I observed was in the peephole optimizer.
Because the one place where it triggers is in the IDE (in FpDebug), if you want a working IDE, then you should compile Lazarus with -O1 if you rebuild it.
---
EDIT (3):
Just to clarify: A 32 bit IDE cross compiling to 64 bit, will badly impact the debugging abilities. Rather use a 64bit IDE compiled with -O1 (in case of rebuilding it / installing packages / just don't change the setting)
Zvoni:
Thx for your answer, Martin.
I searched a bit, and the main issue (before Laz1.8 ) was SEH-handling, but that was before Laz1.8.
A second main issue was, that cross-compiling from Laz/FPC-64Bit to 32-Bit was buggy
At least those two are the main ones popping up researching the topic.
And yes, i know about the hassle about PtrInt, PtrUInt...
Navigation
[0] Message Index
[#] Next page