-
Notifications
You must be signed in to change notification settings - Fork 4
Recommended requirements #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,2 @@ | ||
| test/unit/external_repository | ||
| .ci/micromamba |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,20 +51,20 @@ Prerequisites | |
|
|
||
| We need the following tools: | ||
|
|
||
| - Git 2 or newer (we use 2.36) | ||
| - Bazel 6, 7 or 8 (we recommend version 8.5.0) | ||
| - Clang 16 or newer (we use 16), we use clang-tidy | ||
| - Python 3.8 or newer (we use 3.11) | ||
| - CodeChecker 6.26 or newer (we use 6.26.0) | ||
| - Git 2 or newer | ||
| - Bazel 7.7 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We added bazel 8 support recently. Among other things, we run regular bazel 8 CI jobs for both Ubuntu and Rhel. I suggest we add 8.5.0 or 8.6.0 as well, that is a rather hard requirement from other parties.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, we should make a decision about Recommended requirements.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suggest that it should be 7.7 and 8.6. My understanding is that within a major Bazel release, upgrading to a newer minor release is straightforward. But, with regards to major versions, if "recommended versions" are, in part, according to your comment, those that
beside the first point, both bazel 7 and 8 (and the respective latest minor versions) qualify pretty strongly for that, as there are other teams using these rules that use bazel 8 exclusively. |
||
| - Clang and clang-tidy 21 | ||
| - Python 3.11 or newer | ||
| - CodeChecker 6.27.3 | ||
|
|
||
| If, by chance, Environment Modules (https://modules.sourceforge.net/) | ||
| are available in your system, you can just add the following modules: | ||
|
|
||
| module add git | ||
| module add bazel/6 | ||
| module add clang/16 | ||
| module add bazel/7 | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is only Bazel 7.3.1 in "my" RHEL8 environment, which does not work :( |
||
| module add clang/21 | ||
| module add python/3.11 | ||
| module add codechecker/6.26 | ||
| module add codechecker/6.27.3 | ||
|
|
||
|
|
||
| Getting Started | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,3 @@ | ||
| pytest | ||
| pylint | ||
| codechecker >= 6.26 | ||
|
|
||
| codechecker >= 6.27.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, still does not work :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now addressed in #220