Lazarus Release Candidate 1 of 4.0

[440bx]

Yes, Lazarus trunk v4.99 is now very close to v4.0RC1. You can probably skip the RC1 version.

That simplifies things for me.  Thank you for that info Juha. 

[simone]

Thanks for the great work. But I have a problem. I compiled a complex project (>30KLoc) that I have been working on for over ten years. At the end of the compilation, an access violation occurs, inside the Update method of an Action. Unfortunately, at the moment I can only show a screenshot. I am under Windows 64 bit. Never had any problems with previous versions of Lazarus.

[Martin_fr]

At the end of the compilation, an access violation occurs, inside the Update method of an Action.

At the end of compile? Or when your app runs? The screen shot looks like when your app runs.
This does look like a nil pointer deref => some object is nil. However that may be a nested object.

I recently saw a bit in fpc/rtl where an "<> nil" check was missing inside action list code. Have to remember how that was triggered. (IIRC that happened in the IDE while opening/closing the form designer...)


When you press ok, an that dialog, and open
menu: View > Debug Window > Callstack

What does it show?

[simone]

It's a run time error that arises after compilation, when application starts inside IDE. Outisde the IDE, application freezes at start. Call stack attached. I need further investigations...

[Jonax]

I'm pleased to report that the rc1 4.0 installed nicely on my AMD64-Debian VM.

My current project runs and compiles without problem on 4.0. Though I use no fancy graphics or sound or extras. Just standard components.

Team Lazarus and FPC: thanks for your efforts. Keep up the good work. 

[dbannon]

Unable to build this release of Lazarus with FPC 3.2.3

TRon, better to open a new thread in more appropriate place.
I have no problem building rc1 with fpc3.2.3. Or importing my previous config. My FPC 3.2.3 is stock standard except for two very minor (and irreverent) patches I apply. Have you made any changes to your FPC ?

This has to relate to the problem you had previously.

Davo

[TRon]

TRon, better to open a new thread in more appropriate place.

I deem it appropriate because when not reported I get the "you should have told so timely" response. So, consider it being reported 

The result is from a fresh checkout for both FPC 3.2.3 and Lazarus 4.0rc1 on a pristine system.

Code: Bash  [Select][+][-]

1. admin@test:~$ cd $HOME
2. admin@test:~$ fpc
3. bash: fpc: command not found
4. admin@test:~$ lazarus
5. bash: lazarus: command not found
6. admin@test:~$ startlazarus
7. bash: startlazarus: command not found
8. admin@test:~$
9.  

The reason for the errors can be clearly be identified from the source-code.

[mattias]

The problem is that when I try to use either the startlazarus loader or the lazarus.app directly, I get a message saying "“lazarus.app” is damaged and can’t be opened. You should move it to the Bin."

Mac marks all downloaded zips and executable as unsafe.

 xattr -cr lazarus-darwin-aarch64-4.0.zip

Then unzip.

See https://wiki.freepascal.org/Installing_Lazarus_on_macOS#Step_4:_Binary_Install_of_the_Lazarus_IDE

[mattias]

I've just clicked on Lazarus Mac OS X i386 on the https://sourceforge.net/projects/lazarus/files/ page and it leads to another page that doesn't even have a Lazarus 4.0 RC1 download available.

Could someone explain to me what on earth is going on here?

There is no i386 Mac since more than 15 years. Are you sure you don't want x86-64?

[mattias]

I downloaded the source to Lazarus 4.0RC1 and placed the files in /Applications/Lazarus_4.0. I then used FcpUpDeluxe to install a separate copy of fcp 3.3.1 in /Applications/fcp, added it  to the system path, and restarted my terminal session. Finally, I CDed into /Applications/Lazarus_4.0 and ran make clean bigide. It came up with this...

Code: Bash  [Select][+][-]

1. Hint: (11030) Start of reading config file /Users/carlcaulkett/.fpc.cfg
2. Hint: (11030) Start of reading config file /etc/fpc.cfg
3. Hint: (11031) End of reading config file /etc/fpc.cfg
4. Hint: (11031) End of reading config file /Users/carlcaulkett/.fpc.cfg
5. Free Pascal Compiler version 3.3.1-16756-gb74411cf03-dirty [2024/10/27] for aarch64
6. Copyright (c) 1993-2024 by Florian Klaempfl and others
7. (1002) Target OS: Darwin for AArch64
8. (3104) Compiling fcllaz.pas
9. Fatal: (10022) Can't find unit system used by fcllaz
10.  

AFAIK fpcupdelux installs fpc merely to a directory. In order to use it you must set some env variables. See here:

https://wiki.freepascal.org/fpcupdeluxe#Launching_an_installed_Lazarus_and_fpc_instance

[TRon]

AFAIK fpcupdelux installs fpc merely to a directory. In order to use it you must set some env variables. See here:

For Linux and Windows FPCUpdeluxe will by default create a shortcut and/or desktop icon for Lazarus (depending on whether or not you left it turned on). It will correctly launch Lazarus though if you move the installation around then that will ofc not work anymore as the link does not match the location anymore.

I do not know if this feature works the same for MacOS.

[dbannon]

The result is from a fresh checkout for both FPC 3.2.3 and Lazarus 4.0rc1 on a pristine system.

Code: Bash  [Select][+][-]

1. admin@test:~$ cd $HOME
2. admin@test:~$ fpc
3. bash: fpc: command not found
4. .....
5.  

OK, what have you done with the real TRon, the one who knows how to compile and set a PATH ?

Davo

[dbannon]

Like this -

Code: Bash  [Select][+][-]

1. dbannon@dell:~/bin/Lazarus$
2. dbannon@dell:~/bin/Lazarus$ wget https://gitlab.com/freepascal.org/lazarus/lazarus/-/archive/lazarus_4_0_RC_1/lazarus-lazarus_4_0_RC_1.zip
3. ....
4. dbannon@dell:~/bin/Lazarus$ unzip lazarus-lazarus_4_0_RC_1.zip
5. ....
6. dbannon@dell:~/bin/Lazarus$ cd lazarus-lazarus_4_0_RC_1
7.        
8. dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$ fpc -vh
9. Hint: Start of reading config file /home/dbannon/.fpc.cfg
10. Hint: End of reading config file /home/dbannon/.fpc.cfg
11. Free Pascal Compiler version 3.2.3 [2024/09/20] for x86_64
12. Copyright (c) 1993-2024 by Florian Klaempfl and others
13. Fatal: No source file name in command line
14. Fatal: Compilation aborted
15. Error: /home/dbannon/bin/FPC/fpc-3.2.3/bin/ppcx64 returned an error exitcode
16. dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$
17.  
18. dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$ make bigide
19. ....
20. ....
21. (9015) Linking ../lazarus
22. (1008) 266 lines compiled, 10.4 sec
23. (1022) 4 hint(s) issued
24. make[3]: Leaving directory '/home/dbannon/bin/Lazarus/lazarus-lazarus_4_0_RC_1/ide'
25. make[2]: Leaving directory '/home/dbannon/bin/Lazarus/lazarus-lazarus_4_0_RC_1/ide'
26. make[1]: Leaving directory '/home/dbannon/bin/Lazarus/lazarus-lazarus_4_0_RC_1'
27. dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$

Davo

[dbannon]

I decided to press on and backed up my current Lazarus_aarch64 folder and my ~/.lazarus config folder. I installed FPC 3.2.2 and FPC 3.2.2 Src, although since seeing the comments about using 3.3.1, I've since deleted them again. Meanwhile, I downloaded the Aarch64 version of Lazarus, unzipped the file and placed the Lazarus folder under my /Applications folder and renamed it to Lazarus_4.0.
....

Sigh, you had a working FPC install, one that would probably have built Lazarus 4.0. All you needed to do was to download the Lazarus 4.0-rc1 source, into a suitable dir in you home dir space, un zip it, cd into it and run "make bigide" !

If it built ok, you would then, sensibly, copy your existing Lazarus config, point your new one to the copy (with a lazarus.cfg file) and run "make useride") to build a functionally equivalent Lazarus, setup some way to start it easily and you are done !

Think of Lazarus as just another FPC project, if you can build a project with FPC, you can build Lazarus. If you can run a project built with FPC, you can run your Lazarus built with FPC !

Davo

[Aruna]

Everything I've tested so far works perfectly! I love how users can now choose between the classic floating IDE and the built-in docked version—such a fantastic feature. Huge thanks to everyone involved in making this happen! The screenshot is from something I'm working on—still in beta and not quite finished yet.