eclipse-score / eclipse-score/lifecycle

Validate and adopt the S-CORE global toolchain configuration

Open
#448 1 comment 0 reactions 1 assignee Claimed by @srinivasugithub View on GitHub
good first issue
Dominant language
C++
Stars
6
Forks
34
Avg merge
2d 3h
Merged PRs (30d)
80

Description

## Background

The `module_template` provides a central S-CORE toolchain configuration intended to be shared across repositories.

At the moment, we do not know whether this configuration can be used by this repository as-is, or whether repository-specific additions are still required.

The goal of this issue is to **adopt the central configuration unchanged**, verify whether it works for this repository, and document any remaining gaps or differences.

## Task

Integrate the S-CORE toolchain configuration from `module_template` into this repository and verify that the existing builds and tests continue to work.

The following central configuration must be used **unchanged**:

* the `S-CORE Toolchains (DO NOT MODIFY)` section from `MODULE.bazel`
* `score.bazelrc/score_toolchain.bazelrc`

Do not modify these definitions to make them fit this repository.

Instead, compare the central configuration with the toolchain configuration currently used by this repository.

For every difference, determine whether it is:

* missing from the central S-CORE configuration,
* intentionally repository-specific,
* no longer required, or
* already covered by the central configuration in a different way.

Any repository-specific configuration that is still required must be added separately from the central configuration.

## Expected result

The repository uses the central S-CORE toolchain configuration unchanged.

The issue/PR should contain a short report describing:

* **What works as-is** with the central configuration.
* **What is missing** from the central configuration.
* **What differs** between the central configuration and this repository.
* **What repository-specific configuration had to be added**, and why.
* Any configuration that existed previously but could be removed because the central definition already provides it.

If something appears to be generally required for S-CORE rather than specific to this repository, document it as a candidate for moving into `module_template`.

## Getting started

Use these files from `module_template` as the reference:

* `MODULE.bazel`
https://github.com/eclipse-score/module_template/blob/main/MODULE.bazel
Use the **`S-CORE Toolchains (DO NOT MODIFY)`** section unchanged.

* `score.bazelrc/score_toolchain.bazelrc`
https://github.com/eclipse-score/module_template/blob/main/score.bazelrc/score_toolchain.bazelrc
Use this file unchanged.

* `.bazelrc`
https://github.com/eclipse-score/module_template/blob/main/.bazelrc

Import the central toolchain configuration using:

```text
try-import %workspace%/score.bazelrc/score_toolchain.bazelrc
```

## Acceptance criteria

* [ ] The S-CORE toolchain section from `module_template/MODULE.bazel` is used unchanged.
* [ ] `score.bazelrc/score_toolchain.bazelrc` is used unchanged.
* [ ] The central `score_toolchain.bazelrc` is imported from `.bazelrc`.
* [ ] Relevant repository builds/tests work with the resulting configuration.
* [ ] Repository-specific additions are kept separate from the central configuration.
* [ ] The PR documents central configuration gaps and repository-specific differences.
* [ ] Potential improvements to the central `module_template` configuration are identified.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.