Lazarus Release Candidate 1 of 3.0

[JuhaManninen]

This doesn't seem ZEOS/Mac specific as I'm having the exact same problem ("Can't find DateTimePicker" etc. as in the screenshot) trying to rebuild the IDE on a fresh install of Debian 12 x64 (FPC/Lazarus installed via the .debs). No earlier version of FPC/Lazarus installed. Was trying to install AnchorDocking. If I remove the DateTimePicker packages it will then fail with a similar "Can't find" error on the AnchorDocking unit.

Indeed I can reproduce that. I installed MX Linux "Libretto" RC2, 32-bit version into VirtualBox and installed Lazarus 3.0 RC1 there from .deb packages.
Lazarus starts OK. Then I did a clean rebuild from Tools -> Configure "Build Lazarus" ... and got the same error.
It should be fixed for RC2.
If it happens with MacOS and Linux .deb, it probably happens with other installers, too. Did somebody test with Windows?

Now I can only recommend that you get fixes_3_0 sources from Gitlab and build with "make". It works.
It has additional benefits. Later you can "git pull" to get latest bug fix updates from the branch. No need to wait for RCx versions.
What more, Lazarus can rebuild itself into the same writable source directory tree instead of a config directory. That makes things easier, too.

[Martin_fr]

I haven't tested the issue itself. So the below may not fix it, nor be related to its cause. (Nor do I say, such steps should be necessary..)

I tried a "very clean" install. First deleted everything and then a fresh install.

Does that include your user-config?

Well, actually you can keep the config. But check the config dir for ppu and o files. There are probably some there, and they need to go.

[JuhaManninen]

Does that include your user-config?
Well, actually you can keep the config. But check the config dir for ppu and o files. There are probably some there, and they need to go.

That was my initial thought, too, but tested on a newly installed MX Linux and the first rebuild of Lazarus failed. I started the rebuild right after starting Lazarus. Not compiling any projects in between or anything.

[wp]

Does that include your user-config?
Well, actually you can keep the config. But check the config dir for ppu and o files. There are probably some there, and they need to go.

That was my initial thought, too, but tested on a newly installed MX Linux and the first rebuild of Lazarus failed. I started the rebuild right after starting Lazarus. Not compiling any projects in between or anything.

Did the same on Windows: Fresh secondary installation of v3.0RC1, new config dir, rebuild immediately after installation --> no problems

[hukka]

If it happens with MacOS and Linux .deb, it probably happens with other installers, too. Did somebody test with Windows?

Have been using v3.0RC1 on Windows for a couple of weeks now, installed via the installer, without problem.
I also had a successful install on Linux (different VM) earlier via fpcupdeluxe without IDE build issues.

[JuhaManninen]

I also had a successful install on Linux (different VM) earlier via fpcupdeluxe without IDE build issues.

fpcupdeluxe gets sources from Gitlab. It does not use .deb install packages or similar.
The easiest way to test the coming Lazarus 3.0 release after a failed RC1 installation/rebuild is to load sources from Gitlab and run "make".

This should work :
 $ git clone https://gitlab.com/freepascal.org/lazarus/lazarus.git lazarus
 $ cd lazarus
 $ git switch fixes_3_0
 $ make
 $ ./lazarus &

Note, FPC 3.2.2 and all Lazarus dependencies were installed with the RC1 installation. The installed Lazarus can stay there. The new git clone version is started from its own location, no installation is needed for it. Nice and handy.

"make" (or "make all") builds a minimal Lazarus IDE + some tools like StartLazarus and LazBuild.
You can then install the packages you need in Lazarus, or you can "make bigide" to get a set of packages included in a release version.

FYI, the above git clone process failed in my 32bit MX Linux 23 test for very different reasons. This FPC bug affects x86 32bit :
 https://gitlab.com/freepascal.org/fpc/source/-/issues/39295
I have a nice e-machines mini-laptop which I still want to use but it becomes more and more difficult. Fortunately MX Linux still supports a 32bit CPU. Most other distros have dropped the support.
[Edit] The above process succeeds in MX Linux 21.3. 
It has an older libc version. I will install it to the mini-laptop which is useful even for Lazarus development when I am on the road. The new MX Linux 23 can be used with a future FPC 3.2.4 whenever that comes out. Maybe in 2025...

...

Code: [Select]

Compiling lazres.pp
Linking ./lazres
Warning: "crtbegin.o" not found, this will probably cause a linking failure
Warning: "crtend.o" not found, this will probably cause a linking failure
/usr/bin/ld: /usr/lib/fpc/3.2.2/units/i386-linux/rtl/si_c21.o: in function `SI_C21_$$__FPC_LIBC21_START':
si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x27): undefined reference to `__libc_csu_fini'
/usr/bin/ld: si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x2c): undefined reference to `__libc_csu_init'
Error: Error while linking
Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted


[hukka]

Note, FPC 3.2.2 and all Lazarus dependencies were installed with the RC1 installation. The installed Lazarus can stay there. The new git clone version is started from its own location, no installation is needed for it. Nice and handy.

Excellent, thanks for the build instructions; worked fine. However rebuilding the IDE afterwards still fails for me, this time with IDEOptEditorIntf (see screenshot). This is with a fresh Lazarus config so no stale files from the previous attempts. (Screenshot is from Debian 12 with a Windows visual theme, just to clear any confusion)

EDIT: user error - Lazarus directory setting was still pointing to the .deb installation, changing that to ~/lazarus fixed it. Builds fine now.

[JuhaManninen]

EDIT: user error - Lazarus directory setting was still pointing to the .deb installation, changing that to ~/lazarus fixed it. Builds fine now.

Ah yes, when you have an existing primary config directory, you should either delete it if not needed, or use --pcp= parameter for a secondary config dir. For example :
 $ ./lazarus --pcp=~/.lazarus_fixes_3_0 &
That way you can run many Lazarus versions with their own configurations.
If you only have the failed RC1 installation, you can just delete the primary config ~/.lazarus and it will be recreated.

[cpicanco]

Hi guys, in trunk, I can't find the TStringHelper type

[dbannon]

Ah yes, when you have an existing primary config directory, you should either delete it if not needed, or use --pcp= parameter for a secondary config dir.
....

I often have quite a few lazarus installs at any one time. I ALWAYS create a lazarus.cfg file in the top level directory immediatly after first build and point PCP to a config dir based on the particular version of lazarus there at the time. eg

Code: [Select]

$> echo "--PCP=~/bin/Lazarus/Configs/lazarus-fixes_3_0" > lazarus.cfg
saves a lot of accidents.

Davo

[ssawgift]

Not sure if I am asking too much, but here it is.

Since it is a major upgrade, do you consider it a great chance to update many of the packages to latest?

For example RegExpr unit still uses version 0.9 while its latest is version 1.155 (https://github.com/andgineer/TRegExpr) released about 1 years ago.

[Martin_fr]

RegExpr is part of FPC.  And the latest FPC is 3.2.2.

The Lazarus release does not decide what is inside the FPC release.

[michaelthuma]

Maybe I'm just confused, but Tools-Desktops...-Autosave cannot be turned off. IIRC the feature relied on the Autosave 'section' in the environmentoptions.xml file. Adding the tagged line taken from the current 2.2.6 install didn't help. So the desktop is saved in general and just turning off the option does help, but the setting is ignored/not considered the next time the IDE starts up.

I'd say it's just a minor glitch but could be confusing indeed.

In gerneral 3.0 RC1 works pretty good so far I can see. Well done!

== 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

[TRon]

Maybe I'm just confused, but Tools-Desktops...-Autosave cannot be turned off.

It was already mentioned by user alank and juha mentioned it being fixed in this commit

[alank]

I'm seeing an "Operation not allowed on sorted list." error dialog box appear under the following conditions:

1. Create a project with a single form.

2. With the form selected, click on the "Align" drop down list box in the object inspector.

3. An error dialog appears (see attached).

- 3.0 RC1 built on Fedora 38 Linux/x86_64 w/ Qt5 widget set

The same error seems to occur for every property with a drop down combo box. As can be seen by the attached image, I am using anchor docking and docked form editors.

Update: Issue does not occur for me if I build Lazarus with the Gtk2 widget set.
Update': Issue does occur with the Qt6 widgetset and libqt6pas libraries provided by Davo.

Alan