Forum > Lazarus

Lazarus Release Candidate 1 of 2.2.0

<< < (2/27) > >>

Martin_fr:

--- Quote from: 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.

--- End quote ---

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.

dseligo:

--- Quote from: Martin_fr on July 12, 2021, 04:42:11 pm ---
--- Quote from: 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.

--- End quote ---

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.

--- End quote ---

I reported it: 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.

dseligo:
Two more attachments.

The last one worries me. Doesn't that mean that it will interfere with packages from my other installation?

Martin_fr:

--- Quote from: dseligo on July 12, 2021, 05:13:34 pm ---
--- Quote from: Martin_fr on July 12, 2021, 04:42:11 pm ---Real Default CompilerFilename=C:\FPC\3.2.0\bin\i386-win32\fpc.exe

--- End quote ---
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

--- End quote ---

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".

440bx:

--- Quote from: Martin_fr on July 12, 2021, 04:46:53 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.

--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version