Recent

Author Topic: Lazarus Release Candidate 1 of 2.2.0  (Read 80975 times)

mattias

  • Administrator
  • Full Member
  • *
  • Posts: 176
    • http://www.lazarus.freepascal.org
Lazarus Release Candidate 1 of 2.2.0
« on: July 12, 2021, 01:12:20 pm »
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

  • Sr. Member
  • ****
  • Posts: 386
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #1 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.

When I try to add button to a form I get error:
Code: Text  [Select][+][-]
  1. controls.pp(40,36) Error: unit not found: Types

C:\lazarus_220rc1\lazarus.cfg contains:
Code: Text  [Select][+][-]
  1. --primary-config-path=C:\lazarus_220rc1

Tools, Options, FPC source directory:
Code: Text  [Select][+][-]
  1. $(LazarusDir)fpc\$(FPCVer)\source

Information about the IDE:
Code: Text  [Select][+][-]
  1. Lazarus version: 2.2.0RC1
  2. Lazarus svn revision: 65419
  3. Lazarus build date: 2021/07/08
  4. Lazarus was compiled for x86_64-win64
  5. Lazarus was compiled with fpc 3.2.2
  6.  
  7. Global IDE options:
  8. Primary config directory=C:\lazarus_220rc1
  9. Secondary config directory=C:\lazarus_220rc1
  10. LazarusDirectory=C:\lazarus_220rc1\
  11. Real LazarusDirectory=C:\lazarus_220rc1\
  12. Default CompilerFilename=fpc.exe
  13. Real Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exe
  14. Project CompilerFilename=$(CompPath)
  15. Real Project CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exe
  16. CompilerMessagesFilename=
  17. Real CompilerMessagesFilename=C:\lazarus_220rc1\components\codetools\fpc.errore.msg
  18. FPC source directory=$(LazarusDir)fpc\$(FPCVer)\source
  19. Real FPC source directory=C:\lazarus_220rc1\fpc\3.2.0\source\
  20. WARNING: directory not found
  21. Test directory=C:\Users\Damir\AppData\Local\Temp\
  22. Real Test directory=C:\Users\Damir\AppData\Local\Temp\
  23.  
  24. Working directory=C:\lazarus_220rc1
  25. Application.ExeName=C:\lazarus_220rc1\lazarus.exe
  26.  
  27. Parameters:
  28. C:\lazarus_220rc1\lazarus.exe
  29.  
  30. Environment variables:
  31. =::=::\
  32. =::=::\
  33. ALLUSERSPROFILE=C:\ProgramData
  34. ANDROID_SDK_ROOT=C:\LAMW\android-sdk-windows
  35. APPDATA=C:\Users\Damir\AppData\Roaming
  36. APR_ICONV_PATH=C:\Program Files (x86)\Subversion\iconv
  37. AVR32_HOME=C:\WinAVR-20100110
  38. CARBON_MEM_DISABLE=1
  39. CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
  40. CommonProgramFiles=C:\Program Files\Common Files
  41. CommonProgramW6432=C:\Program Files\Common Files
  42. COMPUTERNAME=VERLAPD
  43. ComSpec=C:\WINDOWS\system32\cmd.exe
  44. DriverData=C:\Windows\System32\Drivers\DriverData
  45. FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer
  46. FPS_BROWSER_USER_PROFILE_STRING=Default
  47. HOMEDRIVE=C:
  48. HOMEPATH=\Users\Damir
  49. LOCALAPPDATA=C:\Users\Damir\AppData\Local
  50. LOGONSERVER=\\VERLAPD
  51. NUMBER_OF_PROCESSORS=8
  52. OS=Windows_NT
  53. Path=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;
  54. PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
  55. PROCESSOR_ARCHITECTURE=AMD64
  56. PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 142 Stepping 10, GenuineIntel
  57. PROCESSOR_LEVEL=6
  58. PROCESSOR_REVISION=8e0a
  59. ProgramData=C:\ProgramData
  60. ProgramFiles(x86)=C:\Program Files (x86)
  61. ProgramFiles=C:\Program Files
  62. ProgramW6432=C:\Program Files
  63. PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
  64. PUBLIC=C:\Users\Public
  65. SESSIONNAME=Console
  66. SystemDrive=C:
  67. SystemRoot=C:\WINDOWS
  68. TEMP=C:\Users\Damir\AppData\Local\Temp
  69. TMP=C:\Users\Damir\AppData\Local\Temp
  70. USERDOMAIN=VERLAPD
  71. USERDOMAIN_ROAMINGPROFILE=VERLAPD
  72. USERNAME=Damir
  73. USERPROFILE=C:\Users\Damir
  74. windir=C:\WINDOWS

440bx

  • Hero Member
  • *****
  • Posts: 2560
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #2 on: July 12, 2021, 02:12:02 pm »
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.
« Last Edit: July 12, 2021, 02:14:17 pm by 440bx »
FPC v3.0.4 and Lazarus 1.8.2 on Windows 7 64bit.

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 9706
  • FPC developer.
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #3 on: July 12, 2021, 04:05:57 pm »
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.
« Last Edit: July 12, 2021, 04:14:50 pm by marcov »

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7529
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #4 on: July 12, 2021, 04:42:11 pm »
I installed it as a secondary install on Windows 10.
When first started it complained something about not finding FPC sources.

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.

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7529
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #5 on: July 12, 2021, 04:46:53 pm »
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.

In the past we were aiming at 4 to 6 weeks.
At the moment we got lots of other stuff going on. So no idea.

Normally with the release of 3.2.2 the minimum version would go to 3.2.0.
However, with various issues on optimizations in the 3.2.x releases, we aim at
keeping at least the LCL at 3.0.4
3rd party packages, or the IDE itself may require 3.2.0.

dseligo

  • Sr. Member
  • ****
  • Posts: 386
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #6 on: July 12, 2021, 05:13:34 pm »
I installed it as a secondary install on Windows 10.
When first started it complained something about not finding FPC sources.

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.

I reported it: https://bugs.freepascal.org/view.php?id=39209

I think some other things are also not right.
When first started, under debugger tab is error 'file not found'. It says: 'A useful setting on Windows systems is: $(LazarusDir)\mingw\bin\$(TargetCPU)-$(TargetOS)\gdb.exe.
In my installation actual path is: C:\lazarus_220rc1\mingw\x86_64-win64\bin

I attached screenshots of first run of Lazarus 2.2.0 RC1.

dseligo

  • Sr. Member
  • ****
  • Posts: 386
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #7 on: July 12, 2021, 05:15:52 pm »
Two more attachments.

The last one worries me. Doesn't that mean that it will interfere with packages from my other installation?

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7529
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #8 on: July 12, 2021, 06:01:34 pm »
Real Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exe
I think some other things are also not right.
When first started, under debugger tab is error 'file not found'. It says: 'A useful setting on Windows systems is: $(LazarusDir)\mingw\bin\$(TargetCPU)-$(TargetOS)\gdb.exe.
In my installation actual path is: C:\lazarus_220rc1\mingw\x86_64-win64\bin

Some issue. You have a 64 bit install, but it found a 32bit fpc.

The fpc it found therefore does not give "x86_64-win64".


440bx

  • Hero Member
  • *****
  • Posts: 2560
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #9 on: July 12, 2021, 06:46:28 pm »
In the past we were aiming at 4 to 6 weeks.
At the moment we got lots of other stuff going on. So no idea.

Normally with the release of 3.2.2 the minimum version would go to 3.2.0.
However, with various issues on optimizations in the 3.2.x releases, we aim at
keeping at least the LCL at 3.0.4
3rd party packages, or the IDE itself may require 3.2.0.
Thank you Martin. 

I asked because I want to make sure that I can still compile/recompile my programs using FPC v3.0.4, as long as I can do that, it's fine with me that the IDE or some packages may require a different version.

The other reason I asked is because I am entertaining the idea of upgrading to Lazarus v2.2 but, I want to keep using the compiler (v3.0.4) I've been using for the last couple of years (IOW, I don't want to re-test a program because it is compiled with a different version of the compiler.)

Thank you for the info.
FPC v3.0.4 and Lazarus 1.8.2 on Windows 7 64bit.

c600g

  • New Member
  • *
  • Posts: 31
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #10 on: July 12, 2021, 07:53:58 pm »
I installed RC1 on my Linux box (KDE Neon, so I used the 64-bit deb files), following these steps:

1. Saved my old .lazarus/ directory to start fresh with the new RC
2. Installed the following packages: anchor docking design, sparta docked form editor, weblaz.
3. Edited Lazarus options for preferred font config, colors, tabs, etc.
4. Installed Lazarus Docked Desktops Studio Plus Complete desktop configuration XML file.

Then, I opened an existing application project to see how well FpDebug worked (the new default debugging back end).

Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.

Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).

Issue #3

One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

Looks as if I will have to continue to use GDB to debug libraries.

Hope this helps!
  Alan

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7529
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #11 on: July 12, 2021, 08:09:18 pm »
Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.
Could you please check, if switching between fpdebug and gdb-debug has an effect an this?


Quote
Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).
Ah, yes. On Linux (at least gtk) the component (not sure which one does the display) does multiline.
FpDebug delivers multiline.
Still, the empty lines are not explained (and the multiline may not be desirable).

Please report. (report in category debugger, so it goes straight to me).
I am busy / partly unavailable in the upcoming days / rest of the month.  But I will see if I can get to this.


Quote
One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

Indeed, but you can switch debugger on a per project base.
It's in the project options (first half).

Though if you use the project between several IDE (eg different PC) then that fails. As the setting stores on OID, that is specific to each IDE (you can of course copy this in the environment opts)

c600g

  • New Member
  • *
  • Posts: 31
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #12 on: July 12, 2021, 08:29:57 pm »
Issue #1

Unfortunately, when Lazarus switched to the default debug desktop upon hitting a breakpoint, Lazarus appeared to be unresponsive. If I hit 'F9' to continue the application, the application would run, but I could not interact with the Lazarus window at all. When I shut down the application, Lazarus was still unresponsive. I could close it down using the WM controls, but that was it.

Doing a bit of experimentation, it seems as if switching to the "debug docked" desktop configuration is causing the issue. If I set the "default docked" desktop as the debug desktop, debugging is possible.

Could you please check, if switching between fpdebug and gdb-debug has an effect on this?

I just tried switching the debugger to gdb in the Project Options, set the debug desktop as "debug docked", and it worked fine. Then I switched it back to IDE-Default (which is FbDebug) and now it works fine as well... ? I'm not sure what I did to resolve the issue, but it appears to be working at the moment.

Issue #2

Using the FbDebug back end, the local variables window does not look correct (see attachment).

Ah, yes. On Linux (at least gtk) the component (not sure which one does the display) does multiline.
FpDebug delivers multiline.
Still, the empty lines are not explained (and the multiline may not be desirable).

Please report. (report in category debugger, so it goes straight to me).
I am busy / partly unavailable in the upcoming days / rest of the month.  But I will see if I can get to this.

Will do.

One of my existing projects is a shared library. It does not appear that I can debug shared libraries using FpDebug, which is consistent with what I see here.

Indeed, but you can switch debugger on a per project base.
It's in the project options (first half).

Though if you use the project between several IDE (eg different PC) then that fails. As the setting stores on OID, that is specific to each IDE (you can of course copy this in the environment opts)

Yes, I noticed that it stores an OID, and will have to set it for each different PC I work on and ignore the difference before committing, I guess.

Thanks again,
  Alan

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7529
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #13 on: July 12, 2021, 08:38:04 pm »
I just tried switching the debugger to gdb in the Project Options, set the debug desktop as "debug docked", and it worked fine. Then I switched it back to IDE-Default (which is FbDebug) and now it works fine as well... ? I'm not sure what I did to resolve the issue, but it appears to be working at the moment.

There are plenty reports from people that using any debugger, have occasionally the desktop freezing on Linux. Especially with breakpoint in certain events (OnMove).

But I understand your desktop (Linux) was fine. Only Lazarus was not.

If you run the IDE from a console/terminal you may catch output from the IDE, if there is a crash or anything.

c600g

  • New Member
  • *
  • Posts: 31
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #14 on: July 12, 2021, 08:53:06 pm »
There are plenty reports from people that using any debugger, have occasionally the desktop freezing on Linux. Especially with breakpoint in certain events (OnMove).

But I understand your desktop (Linux) was fine. Only Lazarus was not.

Correct. It was as if Lazarus was not able to switch to the debug desktop and the visible UI froze, although pressing F9 did cause the application being debugged to resume.
 
If you run the IDE from a console/terminal you may catch output from the IDE, if there is a crash or anything.

If I can reproduce the issue again, I will do that. I've submitted an issue for the FpDebug / Local Variables on Mantis as well.

Cheers,
  Alan

 

TinyPortal © 2005-2018