Forum > Lazarus
Lazarus Release Candidate 1 of 2.2.0
mattias:
The Lazarus team is glad to announce the first 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:
http://wiki.freepascal.org/Lazarus_2.2_fixes_branch
The release is available for download on SourceForge:
http://sourceforge.net/projects/lazarus/files/
Choose your CPU, OS, distro and then the "Lazarus 2.2RC1" directory.
Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_2_0RC1
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 svn tag is
http://svn.freepascal.org/svn/lazarus/tags/lazarus_2_2_0_RC1
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.2RC1 is now stable enough to be used by any one for test purposes.
However many of the fixes and new features that where 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 can not 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 can not 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 RC1.
- 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 RC1. 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
dseligo:
I installed it as a secondary install on Windows 10.
When first started it complained something about not finding FPC sources.
When I try to add button to a form I get error:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---controls.pp(40,36) Error: unit not found: Types
C:\lazarus_220rc1\lazarus.cfg contains:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} -----primary-config-path=C:\lazarus_220rc1
Tools, Options, FPC source directory:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---$(LazarusDir)fpc\$(FPCVer)\source
Information about the IDE:
--- Code: Text [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---Lazarus version: 2.2.0RC1Lazarus svn revision: 65419Lazarus build date: 2021/07/08Lazarus was compiled for x86_64-win64Lazarus was compiled with fpc 3.2.2 Global IDE options:Primary config directory=C:\lazarus_220rc1Secondary config directory=C:\lazarus_220rc1LazarusDirectory=C:\lazarus_220rc1\Real LazarusDirectory=C:\lazarus_220rc1\Default CompilerFilename=fpc.exeReal Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exeProject CompilerFilename=$(CompPath)Real Project CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exeCompilerMessagesFilename=Real CompilerMessagesFilename=C:\lazarus_220rc1\components\codetools\fpc.errore.msgFPC source directory=$(LazarusDir)fpc\$(FPCVer)\sourceReal FPC source directory=C:\lazarus_220rc1\fpc\3.2.0\source\WARNING: directory not foundTest directory=C:\Users\Damir\AppData\Local\Temp\Real Test directory=C:\Users\Damir\AppData\Local\Temp\ Working directory=C:\lazarus_220rc1Application.ExeName=C:\lazarus_220rc1\lazarus.exe Parameters:C:\lazarus_220rc1\lazarus.exe Environment variables:=::=::\=::=::\ALLUSERSPROFILE=C:\ProgramDataANDROID_SDK_ROOT=C:\LAMW\android-sdk-windowsAPPDATA=C:\Users\Damir\AppData\RoamingAPR_ICONV_PATH=C:\Program Files (x86)\Subversion\iconvAVR32_HOME=C:\WinAVR-20100110CARBON_MEM_DISABLE=1CommonProgramFiles(x86)=C:\Program Files (x86)\Common FilesCommonProgramFiles=C:\Program Files\Common FilesCommonProgramW6432=C:\Program Files\Common FilesCOMPUTERNAME=VERLAPDComSpec=C:\WINDOWS\system32\cmd.exeDriverData=C:\Windows\System32\Drivers\DriverDataFPS_BROWSER_APP_PROFILE_STRING=Internet ExplorerFPS_BROWSER_USER_PROFILE_STRING=DefaultHOMEDRIVE=C:HOMEPATH=\Users\DamirLOCALAPPDATA=C:\Users\Damir\AppData\LocalLOGONSERVER=\\VERLAPDNUMBER_OF_PROCESSORS=8OS=Windows_NTPath=C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\PuTTY\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\SafeNet\Authentication\SAC\x64;C:\Program Files\SafeNet\Authentication\SAC\x32;C:\FPC\3.2.0\bin\i386-win32;C:\Program Files (x86)\Subversion\bin;C:\Users\Damir\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Subversion\bin;PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSCPROCESSOR_ARCHITECTURE=AMD64PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 142 Stepping 10, GenuineIntelPROCESSOR_LEVEL=6PROCESSOR_REVISION=8e0aProgramData=C:\ProgramDataProgramFiles(x86)=C:\Program Files (x86)ProgramFiles=C:\Program FilesProgramW6432=C:\Program FilesPSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\ModulesPUBLIC=C:\Users\PublicSESSIONNAME=ConsoleSystemDrive=C:SystemRoot=C:\WINDOWSTEMP=C:\Users\Damir\AppData\Local\TempTMP=C:\Users\Damir\AppData\Local\TempUSERDOMAIN=VERLAPDUSERDOMAIN_ROAMINGPROFILE=VERLAPDUSERNAME=DamirUSERPROFILE=C:\Users\Damirwindir=C:\WINDOWS
440bx:
if I may ask, now that there is a release candidate, what's the typical amount of time elapsed between a release candidate and the actual release ?
Almost forgot, can Lazarus 2.2.0 use FPC v3.0.4 to compile programs ?
Thank you and thank you for all the hard work the team has put and is putting into Lazarus.
marcov:
A default config dir (e.g. $lazarusdir/config) for "other install" would be nice.
The lazarus configuration dialogue also got confused because of a global fpc 3.2.2 install. It selected that, rather than the lazarus\fpc embedded fpc dir for the compiler.
Martin_fr:
--- Quote from: dseligo on July 12, 2021, 01:54:07 pm ---I installed it as a secondary install on Windows 10.
When first started it complained something about not finding FPC sources.
--- End quote ---
It found your compiler under
Real Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exe
But that is a diff version, so the sources are not what they should be:
Real FPC source directory=C:\lazarus_220rc1\fpc\3.2.0\source\
Note the "3.2.0" from the incorrect compiler.
Sources are in 3.2.2.
The question is why it preferred your older fpc.
It is normal that on first start, the config dir is empty
(assuming C:\lazarus_220rc1 was empty)
So there is on compiler patch given.
But it should have first looked into the default path in your install...
Please report that as a bug.
Navigation
[0] Message Index
[#] Next page