Lazarus Release 2.2.2

[jonyrh]

Many thanks to all lazarus devs! 

[Martin_fr]

  can I ask which FPC branch/tag at gitlab this Lazarus release uses ?

For Windows:

Tag release_3_2_2

SHA-1: 0d122c49534b480be9284c21bd60b53d99904346, Branch RevNo: 53220
*  * requiredversion to 3.2.0 and 3.2.2

[d.ioannidis]

Hi,

  can I ask which FPC branch/tag at gitlab this Lazarus release uses ?

For Windows:

Tag release_3_2_2

SHA-1: 0d122c49534b480be9284c21bd60b53d99904346, Branch RevNo: 53220
*  * requiredversion to 3.2.0 and 3.2.2

thank you Martin .

regards,

[Martin_fr]

I just double checked. In my test install (created by the official installer), I went into the fpc ....../units/rtl dir and did

Code: Text  [Select][+][-]

1. ppudump.exe fgl.ppu

and it outputs

Code: Text  [Select][+][-]

1. Analyzing fgl.ppu (v207)

208 appears to be for 3.3.1.

use fpc -va
to see the exact files that fpc tries to load and use....

[dseligo]

Installed.
Kudos to developers.

[Red_prig]

Eh support for specific calling conventions

Code: Pascal  [Select][+][-]

1. ms_abi_default
2. ms_abi_cdecl
3. sysv_abi_default
4. sysv_abi_cdecl

  hasn't made it to release yet.

[Martin_fr]

Eh support for specific calling conventions
  hasn't made it to release yet.

Those sound like FPC features?

Then they will make it, when fpc does a release containing them.
I don't know if that will be 3.2.4 or 3.4.
Nor do I know when either of them will be released.
(You can but that query in the fpc section of the forum, or better (probably better likelihood to be seen by more fpc devs) on the fpc mail list.)

If/When either of them is released, Lazarus is likely to make a release soon after.

[Red_prig]

Eh support for specific calling conventions
  hasn't made it to release yet.

Those sound like FPC features?

Then they will make it, when fpc does a release containing them.
I don't know if that will be 3.2.4 or 3.4.
Nor do I know when either of them will be released.
(You can but that query in the fpc section of the forum, or better (probably better likelihood to be seen by more fpc devs) on the fpc mail list.)

If/When either of them is released, Lazarus is likely to make a release soon after.

These directives have been in the stable fpc branch for a long time (I can’t say from which version), but they are not supported by the lazarus text editor. Parsing errors will cause irritation. I wrote a patch for this case, but it's still in the main branch.

[piola]

Cross debugging used to be an issue.
But it is no longer if you use the 64 bit IDE.
- The 64bit FpDebug can handle 64 and 32 bit projects.
- GDB can do both do, but needs a helper app (which is part of the setup)

Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

[piola]

Thank you very much for the new release! With 2.2.0 I was a little afraid that Lazarus development could be ceased, but I'm happy to see that development is continuing! 👍

[Martin_fr]

These directives have been in the stable fpc branch for a long time (I can’t say from which version), but they are not supported by the lazarus text editor. Parsing errors will cause irritation. I wrote a patch for this case, but it's still in the main branch.

Ok, I see.

The person who applied your patch, has to decide if he deems it "merge-able".

Usually this decision starts with: Is it a bug-fix (then maybe yes, if otherwise safe) or is it a feature (then 99.9% no).

From the description I would deem it a bug-fix.

[Martin_fr]

Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

I haven't tested that, so I don't know.
There is no cross compiler supplied by us.

But from what I hear, if you have a cross compiler for that target, you will need certain library files for it to work.

If FPC gives you a "internal error ...." then this normally always is a bug in FPC that should be reported (at least if it can be reproduced).

However, does the FPC team has an officially released cross compiler for this? (I haven't checked)
And is that the one you use?

If not, you may check on the mail list.

Though, if
- you build it yourself
- you can supply git-SHA and exact commands you used to build it
- you have steps to reproduce the error
then I would think it should be reported.

Because, if you do something that is not supported => you should get a proper error, but not an "internal error".

[Martin_fr]

With 2.2.0 I was a little afraid that Lazarus development could be ceased, but I'm happy to see that development is continuing! 👍

Just monitor https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/main and you will see the progress.

For the fixes branch:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/fixes_2_2
https://gitlab.com/freepascal.org/lazarus/lazarus/-/network/fixes_2_2?extended_sha1=&filter_ref=1

[marcov]

Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

Probably not. You can't crosscompile from a target that doesn't have 80-bit extended to one that does. Or at least that is currently not supported.

Note that codetyphon packages FPC versions that are not stable releases.

[piola]

Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.

Probably not. You can't crosscompile from a target that doesn't have 80-bit extended to one that does. Or at least that is currently not supported.

Note that codetyphon packages FPC versions that are not stable releases.

Yes, that's the exactly the point which I do not understand: From Win64 to Linux64 -> same architecture, so both do not have Extended. But it doesn't work anyway