I installed it as a secondary install on Windows 10.
When first started it complained something about not finding FPC sources.
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.
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.
Real Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exeI 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
In the past we were aiming at 4 to 6 weeks.Thank you Martin.
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.
Issue #1Could you please check, if switching between fpdebug and gdb-debug has an effect an this?
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 #2Ah, yes. On Linux (at least gtk) the component (not sure which one does the display) does multiline.
Using the FbDebug back end, the local variables window does not look correct (see attachment).
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).
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?
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.
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)
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.
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
Windows x64 - lazarus-2.2.0RC1-fpc-3.2.2-win64.exe: parallel install:Isn't that after the installer finished?
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?
Windows x64 - lazarus-2.2.0RC1-fpc-3.2.2-win64.exe: parallel install: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.
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 have numerous seconday installations and this appears from time to time. Writing a new Fppkg config always solved the problem
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?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.
- 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.
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.
Something quite different ... obviously it was misplaced in topic FpDebug, but maybe i might ask here:Are you using 2.2rc1 with fpdebug or gdb?
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).
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.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.
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,Just in case you might be interested, for complex parts of a program I code something like this
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.
I have tried to install the lazreportpdfexport0.9 package on windows 7 32 bit and it gives me the following error:I asked around, I was told https://bugs.freepascal.org/view.php?id=37995
lr_e_pdf.pas(539,19) Error: identifier idents no member "SubType"
lr_e_pdf.pas(540,26) Error: identifier idents no member "URI"
What's wrong with Asserts? They don't work anymore ?
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,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.
will it be reanimated?
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!)
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;
Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.
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?
I have downloaded it from sourceforge.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?
Other mac OS issues:There were some fixes, are they still open?
* 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)
Other mac OS issues:There were some fixes, are they still open?
* 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)
If yes, I have to forward to the mail list.
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..."
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)
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)
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.
Another issue for 2.2 RC1 (About dialog shows SVN line with GIT hash appended)
* https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39297
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.
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)
Will be a download for Windows arm64?
Does exist procedure on wiki how to build it? I will try to bulit it. For performance test (arm64 vs. x86-64 on ARM).Wiki: Not that I am aware of.
I will test Windows 11 on Raspberry Pi 400.
Will be a download for Windows arm64?
It is ideal for Raspberry Pi 400 with Windows 10.
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347I 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 .....
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.
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347Please test with the patch attached to the issue.
Please test with the patch attached to the issue.Changing build mode with:
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 ......
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.
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.
... issues are added as they are suggested here on the forum. ...
Lazarus IDE v2.0.10 r63526Please add to title these information:
Lazarus IDE v2.0.10 r63526, 32 bit, i386-win32Please add this to final Lazarus release.
I have this title in main IDE window in Lazarus:QuoteLazarus IDE v2.0.10 r63526Please add to title these information:
- processor version: 32/64 bit
- project compilation setting: i386-win32, x86_64-win64, etc
Changed title by this comment:QuoteLazarus IDE v2.0.10 r63526, 32 bit, i386-win32Please add this to final Lazarus release.
Do you by chance know when (approx) it last worked?
Please create a bug report.https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39388
2. WILL this release support (FreePascal) cross build for aarch64-FreeBSD ??
1. WHEN WILL BE THE RELEASE, please.
1. WHEN WILL BE THE RELEASE, please.
We are running a bit behind....
what's the situation now? when will be the release? :o
when will be the release? :o
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:
What is Launchpad?
Launchpad is the Ubuntu bug tracker.Ok, thanks. I forgot that.
Sadly, however, unlike other distros, U2110 X still reports it CAN do old systray when it cannot.
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.
RichMemo is no longer maintained on CCR although the files are still there; you must get the version from the author's github (see readme.txt in CCR's RichMemo folder). Or use the version distributed by the Online-Package-Manager (OPM) - it works, I just tested it on Laz-fixes/fpc-fixes
I also tested JVCL from OPM with Laz-fixes/fpc-fixed - it works too. Installation of the CCR version is a bit cumbersome because of the large number of packages. I just installed the JvclAll package which links in all other packages - and this worked again (I am not 100% sure though because my system may be contaminated by previous installations of JVCL); otherwise see the manual installation instruction on the wiki page (https://wiki.freepascal.org/JVCL_Components#Installation).
So please be more specific on what exacty you did, and always report the error message and error location if possible.
In the final release, is the debugging going to support watching the properties of objects in the code?
For example, I tried the new RC1, and when hovering the mouse over a line written edit1.text, the debugger showed a yellow hint written "Edit1.Text = ???". And if I add a watch for "edit1.text", it says "<error:member not found: text>".
I also can't watch the contents of any kinds of lists, such as TStringLists.
Not in Lazarus 2.2.I see, thanks.
This feature needs changes to the compiler. Afaik Joost is working on that.
IIRC, Stringlist can be explored (very rudimentary) in the "debug inspector", by following the FList variable.
With witch version of FPC the Lazarus IDE 2.2 will be built.It will be FPC 3.2.2. The next one will probably use FPC 3.2.4.
Do you think that we will see : lazarus-2.2-fpc-3.2.4 ??