Skip to content

Commit 4b00c4a

Browse files
committed
Prepare release 0.5.0
1 parent 1f91df9 commit 4b00c4a

4 files changed

Lines changed: 12 additions & 10 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ release tags add a leading `v` to the package version.
77

88
## Unreleased
99

10+
## 0.5.0 — 2026-09-13
11+
1012
- Added CMake integration through the packaged `UsePRIK.cmake` helper and a
1113
`prik generate --cmake` standalone-project mode. CMake generates PRIK wrapper
1214
sources as build outputs and owns native compilation, linking, external

‎CITATION.cff‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,5 +11,5 @@ authors:
1111
repository-code: "https://github.com/PyNumLab/prik"
1212
url: "https://pynumlab.github.io/prik/"
1313
license: MIT
14-
version: "0.4.3"
15-
date-released: "2026-08-31"
14+
version: "0.5.0"
15+
date-released: "2026-09-13"

‎docs/user/guide/cmake.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -216,13 +216,13 @@ language must be enabled because every PRIK extension contains generated C
216216
binding code, and Fortran must be enabled whenever the module contributes
217217
Fortran sources.
218218

219-
Select the two compilers from one vendor. A generated binding can include the
220-
Fortran runtime's `ISO_Fortran_binding.h`, which a C compiler from another
221-
vendor does not find: Apple Clang beside a Homebrew GNU Fortran fails to
222-
compile the binding, while GNU `gcc` beside GNU Fortran resolves it. The
223-
toolchain stays CMake's to choose, so name the pair through the usual
224-
`CMAKE_C_COMPILER` and `CMAKE_Fortran_COMPILER`, or `CMAKE_ARGS` when a build
225-
backend drives the configure step.
219+
Use a matching C and Fortran compiler from the same vendor/family.
220+
A generated binding can include the Fortran runtime's `ISO_Fortran_binding.h`,
221+
which a C compiler from another vendor does not find: Apple Clang beside
222+
a Homebrew GNU Fortran fails to compile the binding, while GNU `gcc`
223+
beside GNU Fortran resolves it. The toolchain stays CMake's to choose,
224+
so name the pair through the usual `CMAKE_C_COMPILER` and `CMAKE_Fortran_COMPILER`,
225+
or `CMAKE_ARGS` when a build backend drives the configure step.
226226

227227
Normal Fortran sources and targets carry their link-language requirements
228228
through CMake. For a raw archive or shared library whose language is otherwise

‎pyproject.toml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
44

55
[project]
66
name = "prik"
7-
version = "0.4.3"
7+
version = "0.5.0"
88
description = "PRIK generates native Python bindings from Fortran projects, producing importable extensions and editable .pyi contracts for Pythonic APIs."
99
readme = "README.md"
1010
authors = [

0 commit comments

Comments
 (0)