Dear Fortran enthusiasts, we are excited to announce the release of fpm v0.11.0!
This is primarily a maintenance release, with numerous fixes, performance improvements, and compliance updates. However, we also have some notable new features, including:
HDF5 metapackage support via pkg_config Expanded parsing to include abstract interfaces Improved handling of --example and --target flags Option to install test programs
Additionally, this release brings several Fortran standard compliance fixes, that allow fpm to be built with more compilers, and enhanced CI robustness.
What’s Changed
Some key highlights from this release:
Performance & Fixes
Improved text file reading speed
Prevent memory leaks by always initializing redirect_str
Fix for --target option only running the specified target
install.sh now always bootstraps with fpm v0.8.0
Windows archiver now searches for gcc-ar
Parsing & Standard Compliance
Expanded parsing to support abstract interfaces
Properly handle end program without an explicit program header
Fixed operator(==) conflicts for Intel Fortran Compiler (ifx)
CI & Infrastructure Updates
Metapackage CI now uses macos-12
Improved Ubuntu metapackage CI
Windows-specific fixes for registry uploads
Download
You can grab the latest version from our GitHub releases:
Is the GitHub Actions CI package broken? Just got this:
Run fortran-lang/setup-fpm@v6.1.0
fpm-version: latest
fpm-repository: https://github.com/fortran-lang/fpm
This platform is linux
Fetching fpm from https://github.com/fortran-lang/fpm/releases/download/v0.11.0/fpm-0.11.0-linux-x86_64
Error: Error while trying to fetch fpm - please check that a version exists at the above release url.
undefined
Error: The "path" argument must be of type string. Received undefined
Surely something got broken during the last year, currently I’m working on the homebrew tap that was also broken, I’ll look into that asap. Does that link come from setup-fpm, or should it be in the release assets?
The release asset seems to have a -gcc-12 suffix, no idea why that was added,
Issue appeared during some CI updates, I’ve deployed a fix and hopefully it should be integrated into setup-fpm soon.
Anyways, this means that to use latest one will likely need to upgrade the setup-fpm action version.
I’ll note that the name of the binary in the github release now has -gcc-12 at the end of its name. So if anyone is curling this binary directly from the current release and hasn’t updated the name, they’ll continue to get version 0.10.1: