The Lazarus team is glad to announce the first release candidate of Lazarus 3.0.

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_3.0_release_notes http://wiki.lazarus.freepascal.org/User_Changes_3.2.2

Here is the list of fixes for Lazarus 3.x:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_3_0/

The release is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 3.0RC1" directory.

Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#3_0RC1

Minimum requirements:

Windows:
2k, 32 or 64bit.

FreeBSD/Linux:
gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, qt and qt5 (32 or 64bit).

The gitlab page:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/tree/lazarus_3_0_RC1

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 3.0 fixes branch. The resulting 3.0RC1 is now stable enough to be used by any one for test purposes.

However many of the fixes and new features that were committed since the release of 2.2.6 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 3.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 3.0 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 (3.0), 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

Mattias

Sorry for late response, Qt6 is missing.
Windows: Qt, Qt5, Qt6 (64bit only)
FreeBSD/Linux: Add Qt6.2 for qt6
MacOS: Add Qt6 (64bit only).

zeljko

...

Is 3.0 meant here as current version to publish your project, or should this be done in the current 2.x version ?

Marc

El 3/7/23 a les 13:33, Mattias Gaertner via lazarus ha escrit:

- Compile, debug and run

I don't remember the exact wording but, when converting the settings from lazarus 2.2 (which I copied in a different directory), it offered to use the fpdebug backend.

Then, when compiling a *existing* project, it tells me to use a suitable debugging format (with -gw3 selected, previously I used gdb with -g). I accept but the breakpoints don't work.
I tried the other two options with the same result. With gdb backend and -g the breakpoints work.

With a *new* project the breakpoints work even with the fpdebug backend.

This is under win32, under linux (64 bits), the breakpoints work even in the old project (the same one I used to test under win32).

In both cases (win/linux) I got lazarus' sources with git checking out the tag lazarus_3_0_RC1, "make bigide" then (not without problems) I rebuilt it with my set of packages.

Bye

26.07.2023 17:05, Luca Olivetti via lazarus ?????:

I would recommend to checkout not the tag, but the tip of `fixes_3_0` branch. It already contains a number of important fixes.

If it can still be reproduced with it, please create an issue.

What happens to the breakpoint icon when you start the debugger?

Before you start the debugger, it should have a "?". When you start it, what happens.
You can also check in the breakpoint-windows, if you make the first column wide enough there is some text.

----------
If you remove the breakpoint (can be done while the app is running / after you checked the above), is there a "small blue dot" in the gutter? On the very same line as the breakpoint had been?

Gdb would accept breakpoints at non-code lines.
FpDebug needs the breakpoint on a code line.

Note that
?? if condition then
???? exit;? /// this exit is only a codeline in -O- // with -O1 its optimized away

----------
Are there ways to reproduce it ?
Could sources be shared?

Otherwise I'll send instructions to produce log files.

El 26/7/23 a les 16:36, Maxim Ganetsky via lazarus ha escrit:

I would recommend to checkout not the tag, but the tip of `fixes_3_0` branch. It already contains a number of important fixes. If it can still be reproduced with it, please create an issue.

OK, I did a "git checkout fixes_3_0" then rebuilt the "ide with packages" (from within the old one) with the "clean all" option.

Same problem: the breakpoints don't work in an existing project using the fpdebug backend.

Bye

El 26/7/23 a les 16:50, Martin Frb via lazarus ha escrit:

What happens to the breakpoint icon when you start the debugger? Before you start the debugger, it should have a "?".

Yes, state "?(On)"

When you start it, what happens.

A pause simbol (two vertical white bars in a red circle), state "Pending (On)" (under linux the state is just "Enabled").

You can also check in the breakpoint-windows, if you make the first column wide enough there is some text.

That's what I reported as "state" above

No, not even under linux

Gdb would accept breakpoints at non-code lines. FpDebug needs the breakpoint on a code line.

It's on a code line, not a blank line nor a comment.

Both breakpoints I tested are on an assignment that cannot be optimized away

---------- Are there ways to reproduce it ? Could sources be shared?

The projects I tested no, I'll see if I can find a simpler project with the same issue.

Otherwise I'll send instructions to produce log files.

Bye

El 26/7/23 a les 17:18, Luca Olivetti via lazarus ha escrit:

I found a simple project that I can share but I'm not sure it's a good idea to send it here (the zip file is 143K).

Bye

El 26/7/23 a les 17:26, Luca Olivetti via lazarus ha escrit:

I can reproduce the issue with a lazarus build with "make clean ; make bigide" and a fresh pcp.

Bye

So FpDebug did not find the source file.

The pause is used, because this can happen with DLL. And then the break may get set when the dll is loaded.
I assume that is not the case?

Anything about the filename? special chars? sym links?

Then there are probably 2 files with that name => and the breakpoint is in the other file.

Could that be?

Or could the IDE know the file with a different directory than FPC does ? (though that should still work)

You can send it directly to my mail? lazarus as name, and the 2nd part is mfriebe.de

El 26/7/23 a les 17:42, Martin Frb via lazarus ha escrit:

So FpDebug did not find the source file.

I found the issue: it's the -Xg (use external debug symbols file) option. I wonder why it doesn't work under windows but it does under linux.

Bye

I would still like to see that sample project, if possible. Maybe there is an easy fix.

El 3/7/23 a les 13:33, Mattias Gaertner via lazarus ha escrit:

You can then open that copy in the RC1. Please test:

Now that, with Martin, I found the casue of the problem with the fpbebugger, now I have a different problem: the TSpeedButtons cut the text that previously fit.

See this picture:

https://postimg.cc/k61b0wCx

the upper toolbar is in lazarus 2.6, the lower one with 3.0 RC1.

The rest of the layout of the form seems OK.

Bye

27.07.2023 18:02, Luca Olivetti via lazarus ?????:

Please create an issue and attach a test project there.

El 27/7/23 a les 17:16, Maxim Ganetsky via lazarus ha escrit:

Done

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

Bye