score_basilibs: Update to official release 0.1.2#159
Merged
vinodreddy-g merged 3 commits intoeclipse-score:mainfrom Nov 3, 2025
Merged
score_basilibs: Update to official release 0.1.2#159vinodreddy-g merged 3 commits intoeclipse-score:mainfrom
vinodreddy-g merged 3 commits intoeclipse-score:mainfrom
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
7798c89 to
a2aacfa
Compare
- Rename and updated score-baselibs 0.0 -> score_baselibs 0.1.2 - Handling for injected implicit score-baselibs dependency - Suppress compiler warnings (treated as errors) inherited - Rename all dependencies
a2aacfa to
3a2828e
Compare
|
The created documentation from the pull request is available at: docu-html |
Instead of using llvm from global bazel registry switch to score_toolchains_gcc. Did needed changes to get compilation running.
Adapt the workflow to work with the new toolchain. Currently the coverage report is created manually since the bazel coverage workflow is broken (see eclipse-score/toolchains_gcc#21).
0a63f74 to
ff3d0c4
Compare
Contributor
Author
|
"coverage drop" will be investigated in #160 |
arkjedrz
approved these changes
Oct 31, 2025
| build --@score_baselibs//score/json:base_library=nlohmann | ||
| build --@score_baselibs//score/mw/log/flags:KRemote_Logging=False | ||
|
|
||
| # ToDo: needed for "wrong" implicit dependencies |
Contributor
Author
There was a problem hiding this comment.
I think this is related to a wrong dependency handling in other modules / modules we depend on (but I don't know which one tbh) so we still inherit dependencies to the "old" version of baselibs containing the - instead of _ in the name ... this is why we need to define for both the according flags for building
vinodreddy-g
approved these changes
Nov 3, 2025
atarekra
pushed a commit
to Valeo-S-CORE-Organization/persistency
that referenced
this pull request
Nov 9, 2025
* score_basilibs: Update to official release 0.1.2 - Rename and updated score-baselibs 0.0 -> score_baselibs 0.1.2 - Handling for injected implicit score-baselibs dependency - Suppress compiler warnings (treated as errors) inherited - Rename all dependencies * toolchain: Switch from llvm to score gcc Instead of using llvm from global bazel registry switch to score_toolchains_gcc. Did needed changes to get compilation running. * workflows/check: Update coverage workflow Adapt the workflow to work with the new toolchain. Currently the coverage report is created manually since the bazel coverage workflow is broken (see eclipse-score/toolchains_gcc#21).
Saumya-R
pushed a commit
to qorix-group/persistency
that referenced
this pull request
Nov 19, 2025
* score_basilibs: Update to official release 0.1.2 - Rename and updated score-baselibs 0.0 -> score_baselibs 0.1.2 - Handling for injected implicit score-baselibs dependency - Suppress compiler warnings (treated as errors) inherited - Rename all dependencies * toolchain: Switch from llvm to score gcc Instead of using llvm from global bazel registry switch to score_toolchains_gcc. Did needed changes to get compilation running. * workflows/check: Update coverage workflow Adapt the workflow to work with the new toolchain. Currently the coverage report is created manually since the bazel coverage workflow is broken (see eclipse-score/toolchains_gcc#21).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because of problems with the caching and the size of llvm we also decided in the scope of this PR to switch the toolchain:
This then required an update for the code coverage handling:
workflows/check: Update coverage workflow