Forum > Lazarus
Lazarus Release Candidate 2 of 2.2.0
mattias:
The Lazarus team is glad to announce the second release candidate of Lazarus 2.2.
This release 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.2RC2" directory.
Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_2_0RC2
Minimum requirements:
Windows:
2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.
FreeBSD/Linux:
gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.
Mac OS X:
Cocoa (64bit) 10.12 to 11.4, 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_0_RC2
Last trunk svn revision was r65398.
For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:ftp://ftp.freepascal.org/pub/lazarus/releases/
== Why should everybody (including you) test the release candidate? ==
In the past weeks the Lazarus team has stabilized the 2.2 fixes branch. The resulting 2.2RC2 is now stable enough to be used by anyone for test purposes.
However many of the fixes and new features that were committed since the release of 2.0 required changes to the code of existing features too. While we have tested those ourselves, there may still be problems that only occur with very specific configurations or one project in a million.
Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we cannot fix it.
Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 2.2.x releases. So it may be, that we cannot merge the fix you require. And then you will miss out on all the new features.
== How to test ==
Download and install the 2.2 RC2.
- On Windows you can install as a 2ndary install, that will not affect your current install:
http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus
- On other platforms, if you install to a new location you need to use --primary-config-path
In either case you should make backups. (including your primary config)
Open your project in the current Lazarus (2.0.x), and use "Publish Project" from the project menu. This creates a clean copy of your project.
You can then open that copy in the RC2. Please test:
- If you can edit forms in the designer
- rename components / change properties in Object inspector / Add new events
- Add components to form / Move components on form
- Frames, if you use them
- If you can navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
- Anything else you use in your daily work
BSaidus:
Hello.
I recompiled Lazarus with anchodocking support, then go to codeexplorer and try to jump to different places, units ( clicked on go to unit emplacement ) but it do not do that.
There is many things not working ( jumping) from code explorer to editor.
Thanks
JuhaManninen:
--- Quote from: BSaidus on November 07, 2021, 08:06:46 am ---I recompiled Lazarus with anchodocking support, then go to codeexplorer and try to jump to different places, units ( clicked on go to unit emplacement ) but it do not do that.
There is many things not working ( jumping) from code explorer to editor.
--- End quote ---
It works here.
It must depend on the code. Something confuses the parser. Do Codetools work otherwise with the unit you tested?
Anchodocking should have no effect on CodeExplorer synchronization. Can you please test without it.
BSaidus:
--- Quote from: JuhaManninen on March 09, 1975, 09:07:35 pm ---It works here.
It must depend on the code. Something confuses the parser. Do Codetools work otherwise with the unit you tested?
Anchodocking should have no effect on CodeExplorer synchronization. Can you please test without it.
--- End quote ---
Frankly,I tested a new non saved project.
I'll test later and give more infos.
[Edited to fix quote tags]
BSaidus:
It works well, the code explorer synchronize well with the code.
Tested on saved project.
PS: I used fpcupdeluxe to compile the fixes branche of Lazarus with fpc 3.2.2.
Navigation
[0] Message Index
[#] Next page