Is "FPC_FULLVERSION" not configured properly in some builds?

[vfclists]

I build a new version of Lazarus yesterday with the version from the Help | About box

Lazarus 3.1 (rev lazarus_3_0-140-gd0fda80791) FPC 3.2.3 x86_64-linux-gtk2

and when I compile BGRABitmapPack I get the following errors from the subsequent code

Compile package BGRABitmapPack 11.5.8: Exit code 1, Errors: 3, Warnings: 4, Hints: 8
bgraunicode.pas(1143,19) Warning: function result variable of a managed type does not seem to be initialized
unibitmap.inc(121,5) Error: Duplicate identifier "FResolutionUnit"
unibitmap.inc(121,20) Hint: Identifier already defined in unit FPIMAGE: fpimage.pp at line 121
unibitmap.inc(122,5) Error: Duplicate identifier "FResolutionX"
unibitmap.inc(122,17) Hint: Identifier already defined in unit FPIMAGE: fpimage.pp at line 122
unibitmap.inc(123,5) Error: Duplicate identifier "FResolutionY"
unibitmap.inc(123,17) Hint: Identifier already defined in unit FPIMAGE: fpimage.pp at line 123
unibitmap.inc(127,14) Warning: An inherited method is hidden by "GetResolutionHeight:Single;"

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

1.     {$IF FPC_FULLVERSION<30301}
2.     //Resolution
3.     FResolutionUnit: TResolutionUnit;
4.     FResolutionX,
5.     FResolutionY: Single;
6.  
7.     procedure SetResolutionUnit(AResolutionUnit: TResolutionUnit);
8.     function GetResolutionWidth: Single; virtual;
9.     function GetResolutionHeight: Single; virtual;
10.     {$ENDIF}
11.  

It seems that although the FPC version is 3.2.3 it fails the check for {$IF FPC_FULLVERSION<30301}

Is that a problem or in the debug build or is some feature of the fpcdeluxe I used to build Lazarus?

Could it be that library developer used the wrong string for FPC_FULLVERSION?

Can I set FPC_FULLVERSION some where in the build settings to override this?

[cdbc]

Hi
Well, Of course it fails the check for version >'30301' = 3.3.1 = /trunk/...
Because Its version is namely > '30203' = 3.2.3 = /3.2.2-Fixes/...
So the BGRA-stuff is compiled with trunk-compiler...
edit: Solution: get the trunk = 3.3.1 compiler with FpcUpDeluxe 
edit2: remember to check for gitlab-issues before compiler download!
Regards Benny

[paweld]

get BGRABitmap from dev branch: https://github.com/bgrabitmap/bgrabitmap/tree/dev-bgrabitmap   
this is fixed

[marcov]

Probably it means that some trunk change was merged back to the fixes (3.2.x ) branch, probably during the big merges of december. The $if needs to be adapted for that.

[vfclists]

I think the change may be in Lazarus because the error is not present in Lazarus 3.0 - Lazarus 3.0 (rev lazarus_3_0) FPC 3.2.2 x86_64-linux-gtk2

Which indicates the change must be made in BGRABitmap.

[vfclists]

Hi
Well, Of course it fails the check for version >'30301' = 3.3.1 = /trunk/...
Because Its version is namely > '30203' = 3.2.3 = /3.2.2-Fixes/...
So the BGRA-stuff is compiled with trunk-compiler...
edit: Solution: get the trunk = 3.3.1 compiler with FpcUpDeluxe 
edit2: remember to check for gitlab-issues before compiler download!
Regards Benny

I think the change may be in Lazarus because the error is not present in Lazarus 3.0 - Lazarus 3.0 (rev lazarus_3_0) FPC 3.2.2 x86_64-linux-gtk2

Which indicates the change must be made in BGRABitmap.

[cdbc]

Hi
I think you're right:

Compile package BGRABitmapPack 11.5.8: Exit code 1, Errors: 3, Warnings: 4, Hints: 8

from your first post...
...and I remember f.ex. @lainz was making some changes recently, that's why I thought, it might be better with the trunk-compiler 
Ps.: At least on my lappy, the 3.3.1 compiler is an order of magnitude faster, than the 3.2.2 one.(read compiles to faster running code)
Regards Benny

[MarkMLl]

Can I set FPC_FULLVERSION some where in the build settings to override this?

The problem is likely to be in a library/package which was built outside the scope of your project's build settings.

I think that a more useful question is "how can I expand FPC_FULLVERSION in my code so that I can be absolutely certain what version compiler is being used?".

MarkMLl

[rvk]

I think that a more useful question is "how can I expand FPC_FULLVERSION in my code so that I can be absolutely certain what version compiler is being used?".

Isn't FPC_FULLVERSION not just a constant in FPC ???

Also... you can use a macro to actually print it out.

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

1. program Project1;
2. {$MACRO ON}
3. begin
4.  
5. writeln(FPC_FULLVERSION);
6.  
7. {$DEFINE vs:=writeln(FPC_FULLVERSION)}
8. vs;
9.  
10. readln;
11.  
12. end.

30301
30301

Lazarus 3.1 (rev lazarus_3_0-140-gd0fda80791) FPC 3.2.3 x86_64-linux-gtk2

Does 3.2.3 even exist???
I thought it would have been 3.3.1.

[TRon]

Does 3.2.3 even exist???
I thought it would have been 3.3.1.

To my knowledge:
3.2.2 -> even is release version
3.2.3 -> fixes on top of release version
3.3.1 -> trunk

And that should be it (*) ?

(*) not including new feature branches and perhaps upcoming release version that might be branched/tagged (already)

[Thaddy]

You can also retrieve the EXACT version of main trunk and including the revision.
This is like this for x86_64:

Code: ASM  [Select][+][-]

1. .section .fpc.n_version,"aw"
2.         .balign 32
3. __fpc_ident:
4.         .ascii  "FPC 3.3.1-15198-g71a46465c8-dirty [2024/02/19] for "
5.         .ascii  "x86_64 - Win64"

This is not what you want in most cases, but I already posted how to retrieve this in pure Pascal.
Here is a slightly modified version I published a couple of years ago.

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

1. program testversion;
2. type
3.  TCharArray = array [0..1023] of char; //arbitrary
4. var
5.  __fpc_ident:TCharArray;external;
6. begin
7.   writeln(__fpc_ident);
8. end.

These kind of tricks are not recommended!!!!
It shows the compiler version + the git + if I have modified it myself + compile date + platform.
It seems cross platform, works on Arm32 too.... and on Linux and Windows.
Do not use. A normal user does not need this.

[MarkMLl]

Isn't FPC_FULLVERSION not just a constant in FPC ???

Can't be, it's not documented.

https://www.freepascal.org/docs-html/current/rtl/index-8.html#SECTIONF

Also... you can use a macro to actually print it out.

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

1. program Project1;
2. {$MACRO ON}
3. begin
4.  
5. writeln(FPC_FULLVERSION);
6.  
7. {$DEFINE vs:=writeln(FPC_FULLVERSION)}
8. vs;
9.  
10. readln;
11.  
12. end.

Ah yes, very nice... thanks for that :-)

MarkMLl

[Thaddy]

Yes. But the true full version is différent as I demonstrated.

[Thaddy]

Can't be, it's not documented.

My version is extremely not documented but FULL_VERSION is documented.

[qk]

Probably it means that some trunk change was merged back to the fixes (3.2.x ) branch, probably during the big merges of december. The $if needs to be adapted for that.

+1

My two cents, it might be sufficient to replace all occurrences of

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

1. {$IF FPC_FULLVERSION<30301}

with

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

1. {$IF FPC_FULLVERSION<30203}

into BGRABitmap and BGRAControls packages.

It seems to work.
Regards