What is the current version of FPC?

[Remy Lebeau]

The latest version on www.freepascal.org is 3.2.2 but that version is 4 years old.  Is there a newer version, and if so where can it be downloaded from?

[Remy Lebeau]

Nevermind, I think I found it: https://gitlab.com/freepascal.org

The FPC website is outdated then. It still points to SourceForge instead of GitLab.

[Thaddy]

3.2.2 is still official and current. There is a 3.2.4 RC which is 3.2.3 fixes. These are not packaged.
They also contain just fixes and no major new language features.
FPC has much evolved since the last 3.2.2 release, but that feature set is in main/trunk.
Fixes and main/trunk need to be build from source.

[Remy Lebeau]

Thank you for the info. Good to know. Also, the lack of any new stable package releases (info on 3.2.4 in the FreePascal wiki is several years old) is a little disappointing.

[ALLIGATOR]

You can also use the latest FPC (with all the new features and bug fixes (but also, there may be new bugs, but are there more new ones than old ones that have been fixed - that is the question. In addition, bugs tend to be fixed, and in 3.2.2, no one is fixing anything anymore)) and Lazarus using FPCUpDeluxe. By using this latest version, you are also helping to find new bugs faster and fix them, thereby bringing the release date closer

https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases

[gues1]

I think that @Remy is searching for a new stable release of FPC for his Indy project.
I guess he is working on the project to update it and therefore being compatible with both Delphi and Lazarus / FPC he wanted information to test it with "something" recent.
Normally those who create "packages" keep them compatible with stable versions (present and past as much as possible).

[Thaddy]

Also, the lack of any new stable package releases (info on 3.2.4 in the FreePascal wiki is several years old) is a little disappointing.

There are many of us that accept that the current development branch can also be interpreted as a rolling release.
The lack of resources for the release management and the multitude of platforms that must be build are frankly the only things that hold back a new official release. The fixes branch - which is already locked for a long time - can be assumed highly stable for all major platforms(win,linux,mac, for intel, arm and aarch), but the release depends on other platforms too.
As is the case with many opensource projects, imho building from source is rather the common case and not a special case.
If your mindset can accept the concept of rolling releases, you may be less annoyed if at all.

Just my two cents.

[Thaddy]

I think that @Remy is searching for a new stable release of FPC for his Indy project.

I think that too. The 3.2.2 code for Indy still compiles in higher versions. Also in fixes and main.
I'd recommend he uses main, because it has a much, much higher compatibility with modern Delphi, especially when the rtl is compiled for namespaced units and/or function references and anonymous functions are involved. (this is just the top of the iceberg)
He can also leave the current code as-is.

[Thaddy]

and in 3.2.2, no one is fixing anything anymore))

Can't...(unless it is breaking, which would be a very, very big exception to the rule !)
3.2.3 Fixes is officially locked... and for quite some time.

[gues1]

I think that too. The 3.2.2 code for Indy still compiles in higher versions. Also in fixes and main.
I'd recommend he uses main, because it has a much, much higher compatibility with modern Delphi, especially when the rtl is compiled for namespaced units and/or function references and anonymous functions are involved. (this is just the top of the iceberg)
He can also leave the current code as-is.

I think he is "rewriting" the code with a new version of Indy making important changes, first of all to the SSL features (now in fact delegated to addons external to Indy, even if perfectly integrated), but not only.
So the code will not remain like this obviously but we will try to improve it and maybe make it unique to that of Delphi.
And for this it needs the latest stable release (which it probably thought was newer than 3.2.2).

[Martin_fr]

3.2.3 Fixes is officially locked... and for quite some time.

Doesn't look like that... Last commit to 3.2.3 was May 2025.

You do mean the branch "release_3_2_4-branch", which has its version set to 3.2.4rc1 and which has its last commit from the end of 2024

[Thaddy]

@Martin_fr

Contradiction in terms: that means in effect the RC('s) is(are) not in forward sync with fixes.
Fixes should have been branched 3.2.5 already according to the rules, with backports for final release.
An RC is in effect a frozen version of fixes. fixes should be moved to next fixes version and if an RC requires updating you should back port from 3.2.5 fixes. That's how it should work according to fpc's own rules.

I am at a loss how this came about, because that is imnho a mistake.
You can't go on developing in a branch that is technically closed.
And 3.2.3 was technically closed on arrival of the first RC for 3.2.4.

[Warfley]

I would expect that 3.2.4 will also contain updates to the RTL and FCL packages that have been added which do not depend on new compiler features (or have fallback using compiler switches), but looking at the release_3_2_4 branch it does not seem to have many new things

[Thaddy]

These changes - if they are in 3.2.3/RC will be automatically processed.
That is, apart from new compiler features.

[ALLIGATOR]

Normally those who create "packages" keep them compatible with stable versions (present and past as much as possible).

👍☺️👍