Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions packages/frama-clang/frama-clang.0.0.19~beta/opam
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
opam-version: "2.0"
synopsis: "Frama-C plug-in based on Clang for parsing C++ files"
description:
"This Frama-C plug-in parse C++ files that may contain ACSL++ annotations."
maintainer: "Virgile.Prevosto@cea.fr"
authors: "Virgile Prevosto"
license: "LGPL-2.1-only"
tags: ["formal specification" "C++" "plugins" "ACSL" "ACSL++"]
homepage: "https://frama-c.com/frama-clang.html"
bug-reports: "https://git.frama-c.com/pub/frama-clang/-/issues"
depends: [
"dune" {>= "3.13" & != "3.13.0"}
"frama-c" {>= "32.0~" & < "33.0~"}
"zarith" {>= "1.5"}
"camlp5"
"camlp-streams"
"conf-libclang" {>= "11.0.0" & < "20"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"conf-libclang" {>= "11.0.0" & < "20"}
"conf-libclang" {>= "11.0.0"}

I now realize a new all-green conf-libclang.21 is not going to help here! 😅
Could you explain why there is such a conservative upper bound here?
We generally try to avoid them unless there is a good reason for it https://github.com/ocaml/opam-repository/tree/master/governance/policies#5-strict-dependency-constraints-should-be-avoided---or-preventive-upper-bounds
Up until #28950 conf-libclang.15 was the repo's max version... 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are known incompatibilities with clang 21. I have a branch to work on that, but it is not planned to be merged for this release of frama-clang, especially as it involves some changes to the architecture of the plug-in to better abide with clang's guidelines. Generally speaking, there are very often a few changes in libclang's API that break frama-clang between two major versions, hence the upper bound.

By the way, thanks for your efforts on this topic!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, thanks for clarrifying! Sounds like we should roll a conf-libclang.19 as we also discussed...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added in #28968

"conf-clang"
"conf-cmake"
"odoc" {with-doc}
]
build: [
["dune" "subst"] {dev}
[
"dune"
"build"
"-p"
name
"-j"
jobs
"--promote-install-files=false"
"@install"
"@runtest" {with-test}
"@doc" {with-doc}
]
["dune" "install" "-p" name "--create-install-files" name]
]
dev-repo: "git+https://git.frama-c.com/pub/frama-clang.git"
url {
src:
"https://git.frama-c.com/pub/frama-clang/-/archive/0.0.19-beta/frama-clang-0.0.19-beta.tar.bz2"
checksum: [
"md5=2075190f6b1e760a241117d0b184a0b6"
"sha512=69ec73d483435b549fc9c8b785faeb7baf5968c77d938b5386437202cd42bd492a3e39f6d706ff5422de42183e05054b785e25d4c715fa5e901a566677ebdb5c"
]
}
x-ci-accept-failures: ["debian-11" "ubuntu-20.04"]
Loading