Lazarus

Announcements => Lazarus => Topic started by: mattias on July 12, 2021, 01:12:20 pm

Title: Lazarus Release Candidate 1 of 2.2.0
Post by: mattias 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
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 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.

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
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 440bx 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: marcov 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dseligo 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 (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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dseligo 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?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr 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".

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 440bx 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g 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 (https://wiki.freepascal.org/Debugger_Status).

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

Hope this helps!
  Alan
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr 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 (https://wiki.freepascal.org/Debugger_Status).

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)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g 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 (https://wiki.freepascal.org/Debugger_Status).

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
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr 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.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g 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
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on July 13, 2021, 01:31:25 am
On Linux, QT5 app on Gnome should run under the QT Wayland plugin. And Lazarus apps do drop a message to console when they startup to that effect.

However, when the plugin is installed (eg qtwayland5 in Debian/Ubuntu) and the env var is set, they deliver the same warning and a handful of new ones. All seem to be coming from QT rather than Lazarus but I guess Lazarus code is tickling then up.

Code: [Select]
dbannon@deb-Test-Bull:~/Test$  QT_QPA_PLATFORM=wayland  ./qt5Test-fix
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
This plugin supports grabbing the mouse only for popup windows
This plugin supports grabbing the mouse only for popup windows
This plugin supports grabbing the mouse only for popup windows
This plugin supports grabbing the mouse only for popup windows

Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PeterBB on July 13, 2021, 02:16:52 pm
Thanks for applying #35478. Its missing from the release notes/fixes but included in the code.
https://bugs.freepascal.org/view.php?id=35478   :)


However, #37556 is open, so the fpgui widget set will still not compile in Linux.
https://bugs.freepascal.org/view.php?id=37556   :'(


Regards,
Peter
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 13, 2021, 02:26:49 pm
Windows x64  - lazarus-2.2.0RC1-fpc-3.2.2-win64.exe: parallel install:
choosing a separate install folder and a separate config dir:
At the step "Fertigstellen" (complete the installation) the process simply quits without any message.
-
When startinig now the Lazarus-exe from explorer, i see the "Lazarus-IDE einrichten" (Setup IDE) dialog claiming: "there is a problem with the Fppkg configuration. ()".
If i say "write a new one". it does overwrite the already existing one C:\Users\<the-user-username>\AppData\Local\FreePascal\fppkg\fppkg.cfg
What would be the correct step to go?
--
At this occasion: at previous installations, and now too, during the install procedure i had the error message saying there is an error creating file (access denied):for ssleay32.dll and  libeay21.dll.  I decided to ignore that.  Does that harm?

Thanks a lot!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 13, 2021, 02:54:41 pm
Windows x64  - lazarus-2.2.0RC1-fpc-3.2.2-win64.exe: parallel install:
choosing a separate install folder and a separate config dir:
At the step "Fertigstellen" (complete the installation) the process simply quits without any message.
Isn't that after the installer finished?
Isn't this expected?

Quote

When startinig now the Lazarus-exe from explorer, i see the "Lazarus-IDE einrichten" (Setup IDE) dialog claiming: "there is a problem with the Fppkg configuration. ()".
If i say "write a new one". it does overwrite the already existing one C:\Users\<the-user-username>\AppData\Local\FreePascal\fppkg\fppkg.cfg
What would be the correct step to go?
--
At this occasion: at previous installations, and now too, during the install procedure i had the error message saying there is an error creating file (access denied):for ssleay32.dll and  libeay21.dll.  I decided to ignore that.  Does that harm?

Afaik Fppkg only supports one global config.
That is something that might best be asked on the fpc mail list.

dll:
That may be when you try to install them globally, but do not have admin rights.
For the IDE it is enough to have them locally (online package manager needs them).

If you write your own apps that use them, then you need to put copies into your apps dir.
So should be no harm.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: wp on July 13, 2021, 02:56:03 pm
Windows x64  - lazarus-2.2.0RC1-fpc-3.2.2-win64.exe: parallel install:
choosing a separate install folder and a separate config dir:
At the step "Fertigstellen" (complete the installation) the process simply quits without any message.
When you reach "Fertigstellen" Lazarus is installed at least - that's something! In fact I don't even know what happens when I click "Fertigstellen" - is there a final message "Installation completed"? I don't think so.

When startinig now the Lazarus-exe from explorer, i see the "Lazarus-IDE einrichten" (Setup IDE) dialog claiming: "there is a problem with the Fppkg configuration. ()".
If i say "write a new one". it does overwrite the already existing one C:\Users\<the-user-username>\AppData\Local\FreePascal\fppkg\fppkg.cfg
What would be the correct step to go?
If have numerous seconday installations and this appears from time to time. Writing a new Fppkg config always solved the problem

At this occasion: at previous installations, and now too, during the install procedure i had the error message saying there is an error creating file (access denied):for ssleay32.dll and  libeay21.dll.  I decided to ignore that.  Does that harm?
These are the openssl dlls needed by the online-package-manager for accessing https. The installer gives you the option to install them locally, i.e. to copy them into the folder in which lazarus.exe resides - this should have worked; please have a look; if they are not here OPM will not work. The other option is to install the dlls globally, i.e. to copy them into the Windows\System directory. Depending on your permissions you may not be allowed to do this and you will probably get the error message reported. The only advantage of having the openssl dlls in the Windows\System dir is that you do not have to care about them when you write a program accessing https sites.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 13, 2021, 03:33:34 pm
Martin_fr and wp: thanks for your both's infos!

About some items:
- Yes, i installed via non-admin user (that's normmally my preferred option, unless i have indication or be aware that admin is required)
- Yt a "normal" (singular) install, i was used that, after the file copies, the "setup IDE" dialog appears.
  As well as the possibility to choose the target OS; this time it didn't appear.
- About the two files related to "access denied": yes, obviously expects an admin user.
  But note: previously i noticed no problems so far i got a aware being due tu them. And also could use the OPM from time to time.

I had not been sure if Fppkg config should be better distinct. For the moment i let it stay overwritten. I've a backup, if later needed.
About the choice of the target OS, i assume i'll do it now specifically via the project options.

Sorry for irritations and questions, it had been my first secondary install, so the unsureness.
I could open the project now. Thank you a lot!

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 13, 2021, 03:57:07 pm
- Yt a "normal" (singular) install, i was used that, after the file copies, the "setup IDE" dialog appears.
  As well as the possibility to choose the target OS; this time it didn't appear.

The dialog should appear on first start.

I am not suer what "choose target os". That is not part of that dialog.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 13, 2021, 05:01:25 pm
Martin_fr,  i thought i remembered there had been something like such, but the last install meanwhile happened a couple of months ago ... sorry!  No problem!  Thank you!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Gald on July 14, 2021, 05:35:22 am
Could you please look into this particular issue?

https://bugs.freepascal.org/view.php?id=39015

There are a few things in Object Inspector to be refined and it looks very easy to do.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: esdonis on July 14, 2021, 09:24:31 pm
I have tried to install the lazreportpdfexport0.9 package on windows 7 32 bit and it gives me the following error:

lr_e_pdf.pas(539,19) Error: identifier idents no member "SubType"
lr_e_pdf.pas(540,26) Error: identifier idents no member "URI"
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: JuhaManninen on July 15, 2021, 11:34:11 am
There are a few things in Object Inspector to be refined and it looks very easy to do.
In that case please provide a patch.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 16, 2021, 03:01:44 pm
Something quite different ... obviously it was misplaced in topic FpDebug, but maybe i might ask here:
Small question: i noticed that with 2.2 RC1 "OutputDebugString" does no longer generates output for the event window ("Ereignis-Protokoll"). // OS Windows
I use it oftenly as a little helper for to trace something temporarely, without needing then additional includes (except unit Windows) or logging frameworks.
Is that by intention or can i reactivate a usage of OutputDebugString by a setting?
Debugger info type is still set as before (Dwarf2).
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 16, 2021, 06:22:34 pm
Something quite different ... obviously it was misplaced in topic FpDebug, but maybe i might ask here:
Small question: i noticed that with 2.2 RC1 "OutputDebugString" does no longer generates output for the event window ("Ereignis-Protokoll"). // OS Windows
I use it oftenly as a little helper for to trace something temporarely, without needing then additional includes (except unit Windows) or logging frameworks.
Is that by intention or can i reactivate a usage of OutputDebugString by a setting?
Debugger info type is still set as before (Dwarf2).
Are you using 2.2rc1 with fpdebug or gdb?

IIRC OutputDebugString  is for a debugserver.

gdb (or some gdb versions?) may include that.
Afaik fpdebug not yet.

Personally I use "debugln" and compile the app with a console -WC
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 440bx on July 16, 2021, 07:22:33 pm
IIRC OutputDebugString  is for a debugserver.
A "plain" debugger can respond to the OUTPUT_DEBUG_STRING_EVENT which is the event sent to the debugger to notify it that it received a string from the program being debugged.  It's fairly simple to implement.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 16, 2021, 07:25:13 pm
IIRC OutputDebugString  is for a debugserver.
A "plain" debugger can respond to the OUTPUT_DEBUG_STRING_EVENT which is the event sent to the debugger to notify it that it received a string from the program being debugged.  It's fairly simple to implement.
Yes, IIRC I even saw the docs for how it is send.

Just haven't gotten around yet do add it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 16, 2021, 08:44:49 pm
Would be nice!
Many thanks to you both for attention!
OutputDebugString, as based specifically on an Windows API call, is rather known in the Windows environment.
I like it because it is a handy and easy way to put info to the message window,
without needing to apply (and remove afterwards) additional includes, or to change project options temporarely between the compiles.
Simply code a one-liner, trace your program flow and remove the line afterwards. So it would be nice to see it stay alive and not die, if possible.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 440bx on July 16, 2021, 08:55:54 pm
Just haven't gotten around yet do add it.
That makes sense.  I was fairly sure you knew about it but, just in case, I thought I'd mention it.

I like it because it is a handy and easy way to put info to the message window,
without needing to apply (and remove afterwards) additional includes, or to change project options temporarely between the compiles.
Simply code a one-liner, trace your program flow and remove the line afterwards. So it would be nice to see it stay alive and not die, if possible.
Just in case you might be interested, for complex parts of a program I code something like this
Code: Pascal  [Select][+][-]
  1. if IsDebuggerPresent then
  2. begin
  3.   { if there is no console, create a console, otherwise use the existing console }
  4.  
  5.   { format the string message using whatever functions are appropriate }
  6.  
  7.   writeln(<the formatted string>)
  8.  
  9.   { possibly trigger an int 3 depending on what has happened or a readln }
  10.   { optionally dispose of the console }
  11.  
  12.   { resume execution }
  13. end;
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: jamie on July 16, 2021, 11:10:46 pm
What's wrong with Asserts? They don't work anymore ?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 17, 2021, 12:00:26 am
I have tried to install the lazreportpdfexport0.9 package on windows 7 32 bit and it gives me the following error:

lr_e_pdf.pas(539,19) Error: identifier idents no member "SubType"
lr_e_pdf.pas(540,26) Error: identifier idents no member "URI"
I asked around, I was told https://bugs.freepascal.org/view.php?id=37995
(outdate powerpdf version)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PascalDragon on July 17, 2021, 04:08:14 pm
What's wrong with Asserts? They don't work anymore ?

If all you want is to generate some output if a debugger is present, but keep the program itself running then an Assert would be the wrong functionality to use.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 19, 2021, 01:04:00 pm
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.
(bzw: thanks 440bx for your additinal hint!)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: CM630 on July 19, 2021, 02:23:14 pm
win32richmemoproc.pas from richmemopackage does not compile for me.
Says
win32richmemoproc.pas(335,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>" on cbs.pfnCallback := @RTFLoadCallback;
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: avra on July 19, 2021, 02:29:58 pm
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated?
I have checked it today and it worked. When in Lazarus / Tools / Options / Debugger / EventLog / Messages you check Output checkbox, OutputDebugString('<<<<< It works ! >>>>>') outputs to Debug Output window (I have tested it with a simple button on a form and it's on click event). There are a lot of debug messages so you will have to search for it, but it is there. Your GUI or console application needs to include windows unit and you need to make Output Debug window visible. That's all you need to do on Windows.

For more serious work I do recommend something like MultiLog.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 19, 2021, 03:14:02 pm
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.
(bzw: thanks 440bx for your additinal hint!)

I think it needs gdb currently.

As for FpDebug, not sure if I get to it in time.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 19, 2021, 03:22:35 pm
Thank for your both info!

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: skalogryz on July 19, 2021, 04:26:41 pm
win32richmemoproc.pas from richmemopackage does not compile for me.
Says
win32richmemoproc.pas(335,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>" on cbs.pfnCallback := @RTFLoadCallback;

It appears to be FPC 3.2.2 related
And should have been fixed with this pull request (https://github.com/skalogryz/richmemo/pulls?q=is%3Apr+is%3Aclosed)
Are you pulling your richmemo from github?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 19, 2021, 06:53:15 pm
avra, i don't see those options at the told place   .. even not with the gdb.
Could we exchange a bit some settings?  I'll open an item in the Debugger forum  (but not today).
Thanks!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 19, 2021, 08:20:49 pm
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.

Should work with fpdebug (on windows).
Tested with 64 bit, if someone can check 32bit...

Trunk or fixes branch
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: avra on July 20, 2021, 09:40:13 am
avra, i don't see those options at the told place   .. even not with the gdb.
Be more specific of what you do not see. Output checkbox in "Lazarus / Tools / Options / Debugger / EventLog / Messages" configuration dialogue, Debug Output window, or something else?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: CM630 on July 20, 2021, 09:57:09 am
win32richmemoproc.pas from richmemopackage does not compile for me.
...

It appears to be FPC 3.2.2 related
And should have been fixed with this pull request (https://github.com/skalogryz/richmemo/pulls?q=is%3Apr+is%3Aclosed)
Are you pulling your richmemo from github?
I have downloaded it from sourceforge.
Now I cloned it from github and it works.
Thanks!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 20, 2021, 10:28:50 am
avra, i'll create a separate item for that this afternoon within the debugger forum. because i assume the details might be a bit offtopic here. Thank you!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: d7_2_laz on July 20, 2021, 03:09:52 pm
avra, it's here, for to separate it  from this thread. https://forum.lazarus.freepascal.org/index.php?board=12.0
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g on July 23, 2021, 06:13:42 pm
I'm still working with 2.2.0 RC1 on KDE Neon, 64-bit Linux .DEB files (GTK2 widget build), and I've found a significant UI issue that causes Lazarus to freeze.

In my source code, I am using a Generics.Collections TList<>. If I hover the mouse cursor in the source code editor over the variable declared as type TList<> (call it List), the help hint correctly shows me the the definition of the variable, including the file name and line number where it is declared, etc.

If I hover over the Count property of that variable, it also works as expected.

However, when I hover over a method of an indexed member of that TList<> (e.g. List[0].IsMethod()), the entire Lazarus UI freezes and I must terminate the application and restart.

UPDATE: Just tried it in the Win32/Win64 build as well, and the same thing occurs.

Alan
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on July 26, 2021, 05:54:23 am
macOS Issues

* Read me for FPC binary package says it is for 10.4 Tiger (32 bit) and 10.6 Snow Leopard (64 bit) onwards BUT the FPC source package says it is for macOS 10.12 onwards.

* The FPC source package installs the source files to a directory named:
/usr/local/share/fpcsrc/3.2.0 <<----- Lazarus cannot find this directory and in any event it should be 3.2.2 not 3.2.0 (this was a clean install of Big Sur with no previous Xcode, FPC or Lazarus installations). I renamed the directory and Lazarus was happy and the debugger was correctly configured too which is a major step forward.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on July 27, 2021, 02:02:11 am
Other mac OS issues:

* Secondary installation dialog error (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413142.html#msg413142)

* x86_64 and not aarch64 executables produced by default (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413146.html#msg413146)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 28, 2021, 10:14:24 am
Other mac OS issues:

* Secondary installation dialog error (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413142.html#msg413142)

* x86_64 and not aarch64 executables produced by default (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413146.html#msg413146)
There were some fixes, are they still open?
If yes, I have to forward to the mail list.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on July 28, 2021, 10:33:58 am
Other mac OS issues:

* Secondary installation dialog error (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413142.html#msg413142)

* x86_64 and not aarch64 executables produced by default (https://forum.lazarus.freepascal.org/index.php/topic,55517.msg413146.html#msg413146)
There were some fixes, are they still open?
If yes, I have to forward to the mail list.

I see that the FPC binary and source files have been replaced, but the Lazarus pkg is the same, so the Lazarus-specific issues above remain for RC1.

As to the production of x86_64 executables by Lazarus on aarch64, this is because the Lazarus executable is an x86_64 and not a universal binary with aarch64 (fpc has universal binaries and produces aarch64 binaries by default).

Code: Text  [Select][+][-]
  1. file /usr/local/bin/fpc
  2. /usr/local/bin/fpc: Mach-O universal binary with 3 architectures: [i386:Mach-O executable i386] [x86_64:Mach-O 64-bit executable x86_64] [arm64]
  3. /usr/local/bin/fpc (for architecture i386):     Mach-O executable i386
  4. /usr/local/bin/fpc (for architecture x86_64):   Mach-O 64-bit executable x86_64
  5. /usr/local/bin/fpc (for architecture arm64):    Mach-O 64-bit executable arm64
  6.  
  7. file /Applications/Lazarus/lazarus.app/Contents/MacOS/lazarus
  8. /Applications/Lazarus/lazarus.app/Contents/MacOS/lazarus: Mach-O 64-bit executable x86_64
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on July 28, 2021, 11:52:27 am
macOS x86_64 and aarch64

The notes at https://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes#IDE_Changes do not mention the relocation of the Lazarus IDE "Lazarus > Tools > Options" menu to "Lazarus > Preferences" for macOS.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Alextp on July 28, 2021, 12:36:39 pm
@trev I added this info to the end of that topic.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: ChrisR on July 29, 2021, 02:20:23 pm
Issue:
 Lazbuild defaults to Carbon widgetset (which does not support 64 bit applications) when building applications on 64-bit MacOS platforms (x86-64 and AArch64). Therefore, the build fails. In contrast, the Lazarus GUI defaults to Cocoa widgetset which is built correctly.

To replicate:
 In Lazarus IDE, choose Project/NewProject menu item and press "OK" to create a default application. Choose the Run/Run menu item to show that this runs from the IDE. Optionally you can put a {$IFDEF LCLCocoa} or {$IFDEF LCLCarbon} to convince yourself that the IDE defaults to the modern Cocoa widgetset.

Next, attempt the build the application from the terminal with lazbuild. Note that it fails if run by default, as it selects the Carbon widgetset, but succeeds if the `--ws=cocoa` override is provided. Trunk has the same issue. It would be great if Lazarus 2.2.0 Lazbuild would default to the maintained Cocoa widgetset, mimicking the behavior of the Lazarus IDE.


$ /Applications/Lazarus/lazbuild -v
2.2.0RC1

$ /Applications/Lazarus/lazbuild project1.lpi
Hint: (lazarus) Missing state file of LCLBase 2.2.0.1: /Applications/Lazarus/lcl/units/x86_64-darwin/LCLBase.compiled
Error: (lazarus) unable to create package output directory "/Applications/Lazarus/lcl/units/x86_64-darwin" of package "LCLBase 2.2.0.1"
Hint: (lazarus) normal output directory of package LCLBase 2.2.0.1 is not writable: "/Applications/Lazarus/lcl/units/x86_64-darwin/"
TParsedCompilerOptions.SetOutputDirectoryOverride New=/Users/chris/.lazarus/lib/LCLBase/units/x86_64-darwin
Hint: (lazarus) Missing state file of LCL 2.2.0.1: /Applications/Lazarus/lcl/units/x86_64-darwin/carbon/LCL.compiled
Error: (lazarus) unable to create package output directory "/Applications/Lazarus/lcl/units/x86_64-darwin/carbon" of package "LCL 2.2.0.1"
Hint: (lazarus) normal output directory of package LCL 2.2.0.1 is not writable: "/Applications/Lazarus/lcl/units/x86_64-darwin/carbon/"
TParsedCompilerOptions.SetOutputDirectoryOverride New=/Users/chris/.lazarus/lib/units/x86_64-darwin/carbon
Hint: (lazarus) Compiler params changed for LCL 2.2.0.1
  Old="-MObjFPC -Scghi -O1 -gw -gl -Fi/Applications/Lazarus/lcl/interfaces/carbon -Fi/Applications/Lazarus/lcl/interfaces/carbon/objc -Fi/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/appkit -Fi/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/foundation -Fu/Applications/Lazarus/lcl/interfaces/carbon -Fu/Applications/Lazarus/lcl/interfaces/carbon/objc -Fu/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/appkit -Fu/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/foundation -Fu/Applications/Lazarus/packager/units/x86_64-darwin -Fu/Applications/Lazarus/components/lazutils/lib/x86_64-darwin -Fu/Applications/Lazarus/components/freetype/lib/x86_64-darwin -Fu/Applications/Lazarus/lcl/units/x86_64-darwin -Fu/Applications/Lazarus/lcl/interfaces/ -FU/Users/chris/.lazarus/lib/units/x86_64-darwin/carbon -dcarbon lcl.pas"
  Now="-MObjFPC -Scghi -O1 -gw -gl -Fi/Applications/Lazarus/lcl/interfaces/carbon -Fi/Applications/Lazarus/lcl/interfaces/carbon/objc -Fi/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/appkit -Fi/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/foundation -Fu/Applications/Lazarus/lcl/interfaces/carbon -Fu/Applications/Lazarus/lcl/interfaces/carbon/objc -Fu/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/appkit -Fu/Applications/Lazarus/lcl/interfaces/carbon/pascocoa/foundation -Fu/Applications/Lazarus/packager/units/x86_64-darwin -Fu/Applications/Lazarus/components/lazutils/lib/x86_64-darwin -Fu/Applications/Lazarus/components/freetype/lib/x86_64-darwin -Fu/Users/chris/.lazarus/lib/LCLBase/units/x86_64-darwin -Fu/Applications/Lazarus/lcl/interfaces/ -FU/Users/chris/.lazarus/lib/units/x86_64-darwin/carbon -dcarbon lcl.pas"
  State file="/Users/chris/.lazarus/lib/units/x86_64-darwin/carbon/LCL.compiled"
Hint: (11030) Start of reading config file /etc/fpc.cfg
Hint: (11031) End of reading config file /etc/fpc.cfg
Free Pascal Compiler version 3.2.2 [2021/05/16] for x86_64
Copyright (c) 1993-2021 by Florian Klaempfl and others
(1002) Target OS: Darwin for x86_64
(3104) Compiling lcl.pas
(3104) Compiling ./carbon/alllclintfunits.pas
(3104) Compiling ./carbon/agl.pp
(9009) Assembling agl
(3104) Compiling ./carbon/carbonbars.pp
/Applications/Lazarus/lcl/interfaces/./carbon/carbonbars.pp(16,2) Error: (2023) User defined: only 32 bit cpu is supported
(3104) Compiling ./carbon/carbonprivate.pp
(3104) Compiling ./carbon/carbondef.pp
/Applications/Lazarus/lcl/interfaces/./carbon/carbondef.pp(187,1) Fatal: (10026) There were 1 errors compiling module, stopping
Fatal: (1018) Compilation aborted
Error: /usr/local/bin/ppcx64 returned an error exitcode
Error: (lazarus) Compile package LCL 2.2.0.1: stopped with exit code 1
Error: (lazarus) [TLazPackageGraph.CompileRequiredPackages] "Exit code 1"
Error: (lazbuild) Project dependencies of /Users/chris/Desktop/laz/project1.lpi

$ /Applications/Lazarus/lazbuild --ws=cocoa project1.lpi
Hint: (lazarus) Missing state file of LCLBase 2.2.0.1: /Applications/Lazarus/lcl/units/x86_64-darwin/LCLBase.compiled
Error: (lazarus) unable to create package output directory "/Applications/Lazarus/lcl/units/x86_64-darwin" of package "LCLBase 2.2.0.1"
Hint: (lazarus) normal output directory of package LCLBase 2.2.0.1 is not writable: "/Applications/Lazarus/lcl/units/x86_64-darwin/"
TParsedCompilerOptions.SetOutputDirectoryOverride New=/Users/chris/.lazarus/lib/LCLBase/units/x86_64-darwin
Hint: (lazarus) Missing state file of LCL 2.2.0.1: /Applications/Lazarus/lcl/units/x86_64-darwin/cocoa/LCL.compiled
Error: (lazarus) unable to create package output directory "/Applications/Lazarus/lcl/units/x86_64-darwin/cocoa" of package "LCL 2.2.0.1"
Hint: (lazarus) normal output directory of package LCL 2.2.0.1 is not writable: "/Applications/Lazarus/lcl/units/x86_64-darwin/cocoa/"
TParsedCompilerOptions.SetOutputDirectoryOverride New=/Users/chris/.lazarus/lib/units/x86_64-darwin/cocoa
Hint: (lazarus) Build Project: nothing to do.
Hint: (11030) Start of reading config file /etc/fpc.cfg
Hint: (11031) End of reading config file /etc/fpc.cfg
Free Pascal Compiler version 3.2.2 [2021/05/16] for x86_64
Copyright (c) 1993-2021 by Florian Klaempfl and others
(1002) Target OS: Darwin for x86_64
(3104) Compiling project1.lpr
(9009) Assembling project1
(9022) Compiling resource /Users/chris/Desktop/laz/lib/x86_64-darwin/project1.or
(9015) Linking /Users/chris/Desktop/laz/project1
(1008) 25 lines compiled, 1.3 sec
(1022) 2 hint(s) issued
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: ChrisR on July 30, 2021, 02:15:53 pm
I have posted my lazbuild issue on gitlab:
  https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39293
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on July 31, 2021, 12:11:01 pm
Update

If you have any issue/regression that you believe needs to be addressed before the Release of 2.2 make sure it is reported on the issue tracker (https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues) and it is included in the Version 2.2 milestone (https://gitlab.com/freepascal.org/lazarus/lazarus/-/milestones/2)



This includes any issue already mentioned in this thread (unless already fixed and merged).

If you are unsure of an issue you are welcome to discuss it here on the forum (in this thread or any other). If you do not get feedback then it might be best to just report it. Keep in mind that the later the report, the lower the chances something will be done about it.

Where not obvious, please include (in the issue) the reason, why you believe it should be 2.2.




If you report new issues, you may have the option to set the milestone yourself as a suggestion.

Any properties (milestone, labels, ...) are treated as suggestions, and will be reviewed and removed if not agreed on by a developer.
Because issues are often "high prior" to their reporter, any such "importance" properties will usually just be removed. Those fields are reserved for developers only.

If you can not apply the milestone yourself, post the link to the issue in this thread here.
I will then apply the milestone. It will then be reviewed by a team member who maintains the relevant code section (so if found not a 2.2 issue, it will be removed again)




Please note, all milestone are treated as "loose targets". Issues will be addressed, if our manpower permits. The team will decide at its own discretion if or how long to hold the release for an issue. Or if to move an issues target.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: howardpc on July 31, 2021, 01:21:26 pm
Quote
The team will decide at its own digression if or how long to hold the release for an issue.
Martin, I think you meant  "at its own discretion..."
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: ChrisR on July 31, 2021, 08:40:03 pm
Unable to modify the version 2.2 Milestone. I would be grateful if this issue could be addressed with the 2.2 release
  https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39293
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on August 01, 2021, 02:39:24 am

If you have any issue/regression that you believe needs to be addressed before the Release of 2.2 make sure it is reported on the issue tracker (https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues) and it is included in the Version 2.2 milestone (https://gitlab.com/freepascal.org/lazarus/lazarus/-/milestones/2)


Hey, thats pretty cool !

Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on August 01, 2021, 10:26:04 am
If you can not apply the milestone yourself, post the link to the issue in this thread here.
I will then apply the milestone. It will then be reviewed by a team member who maintains the relevant code section (so if found not a 2.2 issue, it will be removed again)

1. https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39296

2. https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39295

The GitLab Issue Tracker gives me a blank screen in SeaMonkey and Firefox; in Safari it doesn't let me upload images. I can also not set any properties or whatever the items in the right-side list are called.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on August 01, 2021, 10:59:45 am
The GitLab Issue Tracker gives me a blank screen in SeaMonkey and Firefox; in Safari it doesn't let me upload images. I can also not set any properties or whatever the items in the right-side list are called.

It works well in Firefox for me.

But this is not in our control.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on August 01, 2021, 12:08:52 pm
Another issue for 2.2 RC1 (About dialog shows SVN line with GIT hash appended)

* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39297
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: avra on August 01, 2021, 03:34:50 pm
Another issue for 2.2 RC1 (About dialog shows SVN line with GIT hash appended)

* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39297

@trev: I can open all 3 issues you mentioned in Vivaldi, Opera, Edge, Chromium, Maxthon and Firefox and see everything I suppose should be there. Tested on Win10 x64.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: paweld on August 01, 2021, 10:19:15 pm
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39290
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on August 03, 2021, 09:47:56 am
I just installed Lazarus 2.2 RC1 on the latest Intel Monterey macOS developer beta and Lazarus asked for access to:

* Photos;
* Desktop folder;
* Contacts; and
* Calendar.

I'm assuming this is due to some new Apple privacy protections that I've yet to track down.

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g on August 03, 2021, 04:38:07 pm
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39306

Couldn't set the milestone to 2.2, nor could I add any labels.

For me, this issue is a must-fix before 2.2 is released, or else I'll have to use an older version. I've lost too much work due to the complete Lazarus freeze.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dsiders on August 03, 2021, 05:05:45 pm
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39306

Couldn't set the milestone to 2.2, nor could I add any labels.

For me, this issue is a must-fix before 2.2 is released, or else I'll have to use an older version. I've lost too much work due to the complete Lazarus freeze.

The GitLab stuff is still kind of new to me... but I think the labels and such are only maintainable by project members. I could be wrong. IAC, I added the obvious stuff to the Issue. The Assignee can always tweak it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on August 03, 2021, 07:39:18 pm
Afaik, only developers can change milestones/lables on existing issues.
A reporter can apply an initial value when creating the issue (aka suggesting values).

We are still sorting out which Labels to keep.

As far as version goes, only the "Version: ..." indicating in what version the reporter found the issue are currently deemed to stay.
For target, the milestone will serve.

As for any sort of priority, those existed in Mantis but were not used there. So unsure if they are going to be kept, and even if, they will probably have little impact.

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on August 08, 2021, 08:46:19 am
Just added:

https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39318

Summary: man pages not found because located in non-standard location /Applications//Lazarus/install/man/man1/ instead of /usr/local/share/man/man1/.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: m.argenti on August 09, 2021, 07:02:07 pm
Hello,
attached 2 little projects
with laz 2.0.12/3.2.0 it works fine but with laz 2.2.0/3.2.2 it doesn't
The first form load (OnFormClick) a second modal form where there is inside a TImage.
If the mouse it's inside image (OnMouseEnter/OnMouseLeave) it should change the cursor (user defined)

Thank you for any hint

Have a good day :)
Massimiliano
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on August 12, 2021, 07:16:44 am
Newly discovered macOS issues:

* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39330 - Readme file instructions
* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39329 - i386 various warnings
* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39328 - Missing Object Inspector
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: c600g on August 15, 2021, 10:03:35 pm
The Lazarus debugger (using the GDB backend) seems to be extremely slow on my fixes_2_2 build (Kubuntu 21.04 on x86_64). When I place a breakpoint and the debugger stops on it, if I press F8 to step over to the next statement, it will take 7-8 seconds before moving to the next line and displaying the local variables.

command used to build the IDE from source:

make bigide LCL_PLATFORM=qt5

UPDATE: If I compile the IDE with the default GTK2 LCL platform, then the debugger performs as expected without unexpected delays.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: avra on August 21, 2021, 01:48:36 pm
If you report new issues, you may have the option to set the milestone yourself as a suggestion.

Any properties (milestone, labels, ...) are treated as suggestions, and will be reviewed and removed if not agreed on by a developer.
Because issues are often "high prior" to their reporter, any such "importance" properties will usually just be removed. Those fields are reserved for developers only.

If you can not apply the milestone yourself, post the link to the issue in this thread here.
I will then apply the milestone. It will then be reviewed by a team member who maintains the relevant code section (so if found not a 2.2 issue, it will be removed again)

I know this quote was for Lazarus, but I am facing the issue of not being able to apply suggestion labels and linked issues to a new FPC gitlab issue so looking for help anywhere.

As discussed at https://forum.lazarus.freepascal.org/index.php/topic,55924.0.html, I could not find a way to apply labels and linked issues, since there were no (+) and (Edit) buttons that gitlab tutorials mention. Either I am doing something wrong, or it is a permission problem. Could anyone point me in the right direction?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on August 21, 2021, 02:12:47 pm
Afaik, once an issue is created, only members of the team can set/add/edit certain attributes (such as milestone and label).

Reporters in that case can only add a note, asking for it to be done.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Milsa on August 24, 2021, 08:00:02 pm
Will be a download for Windows arm64?

It is ideal for Raspberry Pi 400 with Windows 10.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on August 24, 2021, 08:54:13 pm
Will be a download for Windows arm64?

Unfortunately not. We don't currently have anyone to build/test it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Milsa on August 25, 2021, 07:19:49 pm
Does exist procedure on wiki how to build it? I will try to bulit it. For performance test (arm64 vs. x86-64 on ARM).

I will test Windows 11 on Raspberry Pi 400.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on August 25, 2021, 10:58:33 pm
Does exist procedure on wiki how to build it? I will try to bulit it. For performance test (arm64 vs. x86-64 on ARM).

I will test Windows 11 on Raspberry Pi 400.
Wiki: Not that I am aware of.

The scripts are in the repro/git: tools/installer/win. 

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Marc on August 26, 2021, 09:40:35 am
Will be a download for Windows arm64?

It is ideal for Raspberry Pi 400 with Windows 10.

There are still issues with the compiler for win/arm64. I've not tried recently, but I don't think much has changed. Besides that it would require the latest trunk compiler.

Running Windows 11 on a rpi4 works reasonably ok, most of the hardware is supported (contrary to win10). Since the rpi doesn't meet the windows hardware requirements, you can only run the insider preview until it is released.

Windows 11 has a x86 and a x64 emulator, running x86 or x64 executables is surprisingly smooth

Marc
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 01, 2021, 02:49:11 pm
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

Probably a regression that nobody noticed because i cannot remember having seen this behavior in the past (but I cannot say when exactly it started happening because I'm not doing cross platform stuff every day).

I would not release before this is fixed.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on September 03, 2021, 04:21:25 am
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

Anyway, as I had just built a new build machine that does a lot of cross compiling thought I'd see if I could duplicate his/her issue. Not exactly but something close. This with FPC3.2.2 and Lazarus Trunk, the classic minimal project, that is, no attempt to alter mode, or invoke the cross compiler.  It seems to be associated with a message from Pango about "failed to create cairo scaled font, expect ugly output".  Not particularly ugly but not very informative.  See image below.

So, took the same lazarus trunk current source to my laptop, running the same OS, U20.04 Mate, built it and tested all OK.  Only difference between the two platforms is -
* The 'Build' machine is a fresh install and has cross compilers (to Windows 32/64, Linux 32 and RasPi) installed.
* The Laptop has no cross compilers but a longer history. 

So, it might be a cross compiler issue .....

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dsiders on September 03, 2021, 05:08:35 am
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347
I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

main-2_3 is the development branch. It contains things have not been pulled into fixes_2_2  and included in lazarus_2_2_RC1.

lazarus_2_2_RC1 is a snapshot. It does not have the latest commits to fix errors in RC1.

fixes_2_2 has the commits that will be in lazarus_2_2-RC2 when it gets tagged and published.

Introducing, FPC 3.3.1 into the equation only muddies the waters. Version 2.2 is going to have the latest in the FPC 3.2.X series.

Anyway, as I had just built a new build machine that does a lot of cross compiling thought I'd see if I could duplicate his/her issue. Not exactly but something close. This with FPC3.2.2 and Lazarus Trunk, the classic minimal project, that is, no attempt to alter mode, or invoke the cross compiler.  It seems to be associated with a message from Pango about "failed to create cairo scaled font, expect ugly output".  Not particularly ugly but not very informative.  See image below.

So, took the same lazarus trunk current source to my laptop, running the same OS, U20.04 Mate, built it and tested all OK.  Only difference between the two platforms is -
* The 'Build' machine is a fresh install and has cross compilers (to Windows 32/64, Linux 32 and RasPi) installed.
* The Laptop has no cross compilers but a longer history. 

So, it might be a cross compiler issue .....

"trunk" is not a thing any more. Are you testing main-2_3, lazarus_2_2-RC1, or fixes_2_2? Clears as mud... right?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on September 03, 2021, 08:08:29 am
Yes, sorry, my language was imprecise.  I am using 'main', its not labeled any particular type of 'main'. I see it as the direct replacement of 'trunk'. See image.

I don't normally use the GUI side of Lazarus on my build machine, my build run is all command line. Maybe I need to run up Fixes_2_2, that would be far more relevant, its just that I had just finished building the (VM) machine, thought it useful to confirm or otherwise prof7bit's report. (and I did neither).

Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on September 03, 2021, 08:38:40 am
Yes, I can confirm that Fixes_2_2 does the same thing, my sort of same thing, not prof7bit's.

So, the question is, is it because I am missing something in my install or is it, as prof7bit's experience (perhaps) suggests, an issue related to cross compiling ?  Personally, I cannot see what cross compiling has to do with it but the fact that no one else has yet picked it up says its medium rare, like cross compiling ...

Davo

Edit : I appear to have the same Pango and Cairo libraries and the Liberation Sans font installed on the laptop where I don't see this code tools issue, cannot see anything else relevant.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 03, 2021, 06:19:10 pm
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

Yes, you spotted that correctly.

I have 2 installations on my workstation, usually using fixes-2.2 for daily work and I also have a trunk (main) installation around to see if a bug is already fixed in main or when I need to make a new branch for a merge request.

I first encountered this bug in fixes 2.2 (which is currently a bit ahead of 2.2RC1 and will eventually become 2.2). Then I tested it in main to verify it is not yet fixed there and behaves exactly the same in both branches, and then I made the bug report against main as usual (but I mentioned in the bug report it also affects 2.2).

Later while browsing this forum I thought to myself: 2.2 release is pretty damn close, it woluld be very ugly if it were released without first fixing this bug, so I mentioned it here because I know that the people who can make decisions are reading here.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 03, 2021, 06:35:32 pm

main-2_3 is the development branch.

This is actually not a branch name, it is the name of the latest tag in the current branch, I am using a patched version of fpcupdeluxe which uses "git describe --tags" to generate the revision id. It is searching the current branch backwards until it finds a tag and then outputs the tag name and the number of commits on top of it. There is a tag named "main-2_3" placed somewhere in the main branch at the commit when the version number was bumped, so "main-2_3-321-g5ae19e4e" means 321 commits after the "main-2_3" tag.

The branch itself is actually called "main", its name just doesn't appear in the revision id.

So this bug report was made on the bleeding tip of the main branch.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: JuhaManninen on September 04, 2021, 12:36:36 pm
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347
Please test with the patch attached to the issue.
I have been busy with other tasks and not yet committed any code into the new official GitLab repo. I must recollect how to do it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 04, 2021, 01:53:03 pm
Please test with the patch attached to the issue.
Changing build mode with:
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: walkin-corpse on September 05, 2021, 12:21:17 am
Having plans to fix the wrong behavior of InstantFPC-apps in Windows?
If I start it tells "cannot find <path>\program1.exe". But there's only program1.pas and it running ok if started with "instantfpc program1.pas".
Is it bug or whatever?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on September 05, 2021, 06:07:14 am
Yes, I can confirm that Fixes_2_2 does the same thing, my sort of same thing, not prof7bit's.

So, the question is, is it because I am missing something in my install ......


OK, my previous post was misleading, the issue I spotted has nothing to do with the one from prof7bit.

I just built a new U2004 Mate VM and I installed FPC322 (from Deb) and trunk (sorry, Main), Fixes_2_2 and Lazarus_2_0_12, (no cross compilers) all from source and all exhibit the same problem, as shown in the screen dump further up this thread.

So, mine is an 'install issue', and does not belong in this thread. It seems (?) Ubuntu 2004 now arrives with some dodgy font information that can be corrected by refreshing the font cache. (clean out local cache first) -

Code: Bash  [Select][+][-]
  1. rm -rf ~/.cache/fontconfig
  2. sudo fc-cache -r -v

I have no idea why this was necessary but its repeatable using U2004 Mate in a VM ......

Davo









Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: mrmaxmusterman on September 05, 2021, 05:42:25 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.

Are there any updates as far as the release date of Lazarus 2.2 goes?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 05, 2021, 06:12:13 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.

Are there any updates as far as the release date of Lazarus 2.2 goes?

In the Milestones view on Gitlab it lists 366 Bugs to be fixed before 2.2. Yesterday it was 365.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: mrmaxmusterman on September 05, 2021, 06:36:25 pm
In the Milestones view on Gitlab it lists 366 Bugs to be fixed before 2.2. Yesterday it was 365.

But it also says that there are only 19 issues open and 347 are already closed and that the Milestone is 94% complete.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on September 05, 2021, 06:40:26 pm
As indicated earlier the issues are added as they are suggested here on the forum.
So they should at least be noted by the maintainer of the affected code.

They may still be moved to the next release.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: chikega on September 06, 2021, 09:40:06 pm
Thank you for all the hard work for this release  :)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PeterBB on September 09, 2021, 07:29:39 pm
... issues are added as they are suggested here on the forum. ...

I would like to suggest https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39354 (https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39354)
be added to issues now that the bug been recovered from its loss during the move to git.

I gather that https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/35478 (https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/35478) is included,
but without 39354, the widgetset will still not compile on Linux.

It broke with FPC 3.2.0, but can only be fixed in Lazarus.

The bug report includes a trivial patch to fix.

Cheers,
Peter
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PeterBB on September 10, 2021, 03:43:03 pm
I have built RC1 on Arch Linux OK by modifying the existing PKGBUILD.

Attaching here.


Cheers,
Peter

P.S.  Had to add .txt extension to upload. Rename before trying to use!
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Milsa on September 18, 2021, 01:29:34 pm
I have this title in main IDE window in Lazarus:
Quote
Lazarus IDE v2.0.10 r63526
Please add to title these information:
- processor version: 32/64 bit
- project compilation setting: i386-win32, x86_64-win64, etc
Changed title by this comment:
Quote
Lazarus IDE v2.0.10 r63526, 32 bit, i386-win32
Please add this to final Lazarus release.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on September 18, 2021, 01:47:15 pm
I have this title in main IDE window in Lazarus:
Quote
Lazarus IDE v2.0.10 r63526
Please add to title these information:
- processor version: 32/64 bit
- project compilation setting: i386-win32, x86_64-win64, etc
Changed title by this comment:
Quote
Lazarus IDE v2.0.10 r63526, 32 bit, i386-win32
Please add this to final Lazarus release.

I don't think this will make it. (for starters its a new feature, not a bug fix)

It's not (no longer) an option of adding just a (few) checkbox(es).
There are to many bits of info that could be toggled, and then there is the question of ordering....

So what we need is an option to specify the title using the IDE variables that are also used in path info.
like: $(TargetCPU)
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Milsa on September 18, 2021, 05:28:02 pm
Ok, please add it in future.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on September 18, 2021, 07:50:36 pm
Check, and if there is no feature request yet (bugtracker) then add one.

Then if anyone has time and is interested in it.....
Or contribute to it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 21, 2021, 07:59:29 pm
Is it only me or is the dialog for configuring the syntax colors broken (fixes and main)?

* Select a theme you usually don't use (for example Twilight to not break anything)
* change one of the colors
* click ok

-> color has changed, this is OK so far.

* Open the dialog again, click on "Reset all" (top button panel)

-> strange things happen, color is not reset to scheme default, instead colors in the left sidebar are jumping around and it loses the ability to click into the example synedit to select a syntax element.

I tried the same with main, symptoms are similar, and even got it to segfault.

I have anchordocking installed, and also using the Desktops feature for having a separate window layout during debug, if that makes any difference (it does affect storage of some settings), did not yet test without it.

Am I using it wrong? The "reset all" button should reset all colors to the ones defined in the selected scheme xml, shouldn't it? Or did I just find a nasty bug? I'm going to test more and maybe file an issue tomorrow if nobody else did it yet.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on September 21, 2021, 08:15:02 pm
It happens without anchordocking too.

Please create a bug report.

Do you by chance know when (approx) it last worked?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 21, 2021, 08:21:45 pm
Do you by chance know when (approx) it last worked?

No, unfortunately not. I have not played around with color themes for at least a year, only recently felt the need to get some fresh colors and noticed this effect only by accident (always avoided the reset button when making new themes).
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 22, 2021, 09:08:12 am
Please create a bug report.
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39388
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 22, 2021, 10:41:10 am
I identified two consecutive commits on the fixes branch:

2019-05-01 90ecaf0 broken
2019-05-01 ff9c822 OK

Btw: I needed FPC 3.0 to build these old versions, could not get it to build with 3.2
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on September 22, 2021, 11:02:05 am
For some strange reason the bug will NOT disappear if I use current fixes and just revert 90ecaf0, it won't make any difference.

But it will work reliably when I checkout the complete source tree of ff9c822 and build it and the bug will come into existence when I checkout the immediately following 90ecaf0 and build it.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: BSaidus on September 23, 2021, 02:59:39 pm
Hi,
Execuse me for this but, I'll ask anyway  ::)

     1. WHEN WILL BE THE RELEASE, please.
     2. WILL this release support (FreePascal) cross build for aarch64-FreeBSD ??

I'm excited .
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PascalDragon on September 24, 2021, 09:05:20 am
     2. WILL this release support (FreePascal) cross build for aarch64-FreeBSD ??

Support for aarch64-freebsd is only available in the development version of FPC. If you install 3.3.1 you can use aarch64-freebsd already now.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on September 24, 2021, 01:03:25 pm
     1. WHEN WILL BE THE RELEASE, please.

We are running a bit behind....
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Milsa on October 11, 2021, 06:13:41 pm
Do you planning RC2 or final release?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: 12398890 on October 14, 2021, 10:51:34 am
     1. WHEN WILL BE THE RELEASE, please.

We are running a bit behind....

what's the situation now? when will be the release? :o
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: PascalDragon on October 14, 2021, 01:30:50 pm
what's the situation now? when will be the release? :o

The release will be when it's finished. Questioning about it doesn't speed up things.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: Martin_fr on October 14, 2021, 05:25:53 pm
when will be the release? :o

There are currently time restraints with some individuals from the build team. This makes it harder to coordinate things. Hence the actual release process has made very little advances since we announced.

I am afraid, it may be another couple of weeks...
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: trev on October 15, 2021, 12:39:13 am
Like any sane programmer, I'd rather it is released when it is ready and not before :-)

For those who can't wait for some reason, ther4e's always fixes and main (trunk) branches for your programming delight.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: JuhaManninen on October 15, 2021, 02:23:17 am
The fixes_2_2 branch is ready for release, meaning serious crash bugs have been fixed and there is no pending work with any issue.
Some minor bugs may get fixed before the release build actually happens, but the fixes_2_2 branch can now be recommended for everybody. It is easy to build with FPC 3.2.2 on common platforms.
Title: Re: Lazarus Release Candidate 1 of 2.2.0 Systray
Post by: dbannon on October 18, 2021, 10:00:22 am
I am seriously sorry to raise this issue this late in the process. But its prompted by the recent release of Ubuntu 21.10.  For some time now, the Lazarus SysTray has worked in two modes on Linux, either using the traditional SysTray or, added a few years ago, the AppIndicator model.  Sensibly, we test for the existence of traditional system tray and default to it if it looks OK to do so. 

On most current distributions, that test fails and they end up using the AppIndicator.  Ubuntu and its derivatives has been an exception, the test says "Yep, I can do Traditional SysTray" and it does it, well, until now.

Sadly, the release of Ubuntu 21.10 has broken that pattern. It claim to be able to use the SysTray and while it displays the icon, the popup menu appears in what seems a random place. Its a Wayland issue IMHO.

I believe that the solution is to change the default, U2110 and most current distributions can do the AppIndicator fine and its probably time that happened. Some old installs will have trouble with that approach, I suggest there will be many, many times more U2110 (and derivatives) users than people using, for example, Ubuntu 16.04.

The AppIndicator model works fine for other major distributions I have tested, Fedora, SUSE, Debian.

The default decision, which ever it is, can be overridden by setting an env variable before starting a Lazarus app, eg LAZUSEAPPIND=YES   (or NO, INFO).

So, my question is, should I rush a quick change to the default decision, choosing AppIndicators instead of traditional SysTray to try to get into Lazarus 2.2 or not ?  It will involve no really new code, just a reversal of the decision about which path to choose first.

And, yes, I have logged a bug report with Launchpad, I did so several weeks ago when I saw this problem in a beta release. No response ....

Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on October 19, 2021, 03:24:56 am
Further to my question about Linux SysTray -

I have attached a patch and tested my suggested solution on current Ubuntu 21.10 Gnome and Mate, Debian Bullseye Gnome and Mate, Fedora 34 Gnome and on older systems, Ubuntu 16.04, MXLinux 193 (KDE and XFCe)

All appear to work as expected. The older systems can use the AppIndicator model "out of the box", they have the Unity Based AppIndicator installed and can be forced back to the traditional System Tray with the env var.  Newer systems seem to be using the Ayatana AppIndicator and most do not work as expected when forced back to traditional System Tray.

Please remember that the Traditional System Tray was a richer model than AppIndicator provides, the recommendation, for some time now, has been to use only a popup menu, no right click, no animation in the icon etc. Don't blame me, its the Gnome people and their preference for a "simpler UI"

For sake of discussion, if we don't make this change, anyone using System Tray on Ubuntu 21.10 and later will need to start their apps with

Code: Bash  [Select][+][-]
  1. LAZUSEAPPIND=YES ./myapp <enter>

Try telling your end users about that !  In some (actually very few today) cases, this is a change in behavour, so a 2.2 release is when it should happen. There is every reason to assume it must happen sooner or later.

EDIT: My patch does not introduce any new code. It removes a test where we ask X if it can do traditional systray and alters the debug messages that appear only when EnvVar is used. From memory, that X test was controversial when I added it to the unit a year or so ago. It was then intended (by me) to only be transitional.

EDIT2 : sorry, a hunk fails in that patch, I had a debug statement I forgot about.  So SysTray.patch works but does not clean out unnecessary code.  The new, SysTray21a.patch does a better job !
Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0 Systray
Post by: JuhaManninen on October 19, 2021, 05:38:31 pm
And, yes, I have logged a bug report with Launchpad, I did so several weeks ago when I saw this problem in a beta release. No response ....
Where is the bug report?  I cannot find it in the tracker:
 https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues
What is Launchpad?
Title: Re: Lazarus Release Candidate 1 of 2.2.0 Systray
Post by: prof7bit on October 19, 2021, 05:43:00 pm

What is Launchpad?

Launchpad is the Ubuntu bug tracker. The only person who will (or won't) act on this is the one who is packaging Lazarus for Ubuntu. He will then either report it upstrem or patch it only for Ubuntu (and maybe (or not) send the patch upstream) or do nothing at all.

This should really be reported in the official Lazarus gitlab repository where dozens of active devs are reading.
Title: Re: Lazarus Release Candidate 1 of 2.2.0 Systray
Post by: JuhaManninen on October 19, 2021, 06:08:10 pm
Launchpad is the Ubuntu bug tracker.
Ok, thanks. I forgot that.

dbannon, do you have a test app to copy here. I don't have any at least in this machine. I will test it in my Manjaro Linux, too.
How about LCL-GTK3?
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on October 20, 2021, 01:12:13 am
Thanks Juha, in reverse order -

GTK3 should not be an issue, when I did the last Systray update for GTK3 we did not consider the traditional SysTray at all. From memory.

I'll make a test app later today (my time), cannot do it right now, sorry, bit pushed for time.  But easy test, in designer drop a SysTray on the form, give it a an icon and assign a popup menu (thats important, the SysTray must have aan icon and a popup menu with at least one menu item).

Compile and run, on U2110 Gnome, the menu will popup but not where the user expects it.

@prof7bit, to clarify, two possible fixes for this situation -
1. Get Ubuntu to reverse decision to stop supporting old Systray. As they are the last distro to support it, seems unlikely. the issue is within the Desktop, Lazarus does what Lazarus has always done.
2. Apply my patch. its not something for the Lazarus packagers at Debian (or Ubunbu), then apps make with the patched Lazarus will work as expected.  If we push the change I suggest to our Lazarus, eventually Debian will pick up that (they only take releases, never trunk or fixes) and once the fix is in Debian, Ubuntu will use it with their next release.

So, we can assume that Ubuntu has stopped tweaking Gnome to support the old Systray model. I doubt they will reverse that decision. They have also stopped shipping their own Unity based Appindicator, they now appear to ship Ayatana. Sadly, however, unlike other distros, U2110 X still reports it CAN do old systray when it cannot. So the autodetection code I had in there is useless. But its way past time we defaulted to AppIndicator anyway.

In the mean time, applications built using distro lazarus will have problems, packages built from "our" Lazarus will be OK.  For my app, for example, to build in the Debian repo, I will have to try and apply my patch live during the remote build, no idea if I can even do that. Sigh...

Sorry if my post sounds a bit garbled, in a hurry....

 Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: prof7bit on October 20, 2021, 08:41:30 am
Sadly, however, unlike other distros, U2110 X still reports it CAN do old systray when it cannot.

Yes, this sounds like a bug in Ubuntu. Probably nobody there noticed it because the overwhelming majority of applications nowadays use the new API anyways and those few that are too old and still don't support it also won't query which systray API they should use because they are not aware of the change at all.

And I agree Lazarus should also use the new API by default. I remember may years ago (too many to count them) Ubuntu already started aggressively phasing out the old API and most applications just dropped the old one entirely and never looked back.

Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on October 20, 2021, 09:32:41 am
TrayIcon Component on Linux

OK, here is a test app, much as I described but has the added 'feature' of asking X can it, or cannot it not do traditional systems tray. But, as we know, in U2110 at least, X lies !

It has a GTK2, GTK3 and Qt5 modes. In my system here, all work fine in my U2004 Mate machine but on U2110 Gnome the GTK3 version crashes and, as noted, in the GTK2 version, the TrayIcom Menu will popup in the wrong place, apparently randomly, if LCL is unpatched.

(The patch does nothing for GTK3, not sure whats happening there but a different issue. If its TrayIcon, I will look into it but not immediately.)

Davo
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: JuhaManninen on October 20, 2021, 11:18:56 am
I applied the patch in 99e4bd2515. It will be merged to 2.2.
Yes, it improved the menu position of a GTK2 app under my KDE, although it was not totally bad even earlier.
The popup menu opens also with left mouse button. Is it intentional? The QT5 version opens popup only with right button.
The app compiled for GTK3 works here, too, identically with the GTK2 app.
Title: Re: Lazarus Release Candidate 1 of 2.2.0
Post by: dbannon on October 20, 2021, 12:31:38 pm
I applied the patch in 99e4bd2515. It will be merged to 2.2.
Brilliant !  Thanks, really sorry I did not pick it up earlier.

Yes, it improved the menu position of a GTK2 app under my KDE, although it was not totally bad even earlier.
Its mainly a problem on systems using Gnome on Wayland. On my test VM, it pops up anywhere. It was a problems when Wayland first appeared, particularly on Fedora, when people where making Gnome plugins to bring back the old SysTray. In the name of simplicity, Gnome had been trying to stamp out SysTray for some time. Trouble is that Gnome is the default Desktop for the big distros, Fedora, Ubuntu and SUSe.

The popup menu opens also with left mouse button. Is it intentional? The QT5 version opens popup only with right button.
I am not sure. One of the declared aims of the System Tray replacements, the AppIndicators, was that all you could do was respond to a click, you cannot get a right click back, a double click, a drag and so on. On some desktops a right click is reserved for configuring the panel the icon sits in, others its just sent back indistinguishable from a left click.
The app compiled for GTK3 works here, too, identically with the GTK2 app.
Yes, it works fine on my desktop too. I have no idea whats wrong on U2110. I suspect it might be that my code that queries X is to blame, so another reason to get rid of it from LCL.

update: Hmm, still on U2110 and GTK3 version. Bypass my X code and it no longer crashes but it does not work well at all.  No sign of the checkbox and the text in the Memo is far too tiny to read. A way to go with GTK3 I am afraid. I don't think it relates to TrayIcon but will make sure.

EDIT: No, those strange behaviours in GTK3 do not relate to TrayIcon. GTK3 is one sick puppy !

Davo
TinyPortal © 2005-2018