Skip to content

Conversation

@dpiparo
Copy link
Member

@dpiparo dpiparo commented Jan 12, 2026

This PR decouples the concept of plarform and platform configuration. If no platform configuration is specified, the default platform configuration is picked. Otherwise, a special one, <platform>-<config label>.txt is picked.
This has multiple benefits, at least:

  • Simpler yml files for steering builds
  • Same PR, scheduled and workflow dispatch builds (modulo inlined overrides in the yml, as usual) *.
  • Possibility to use the same platform (container) for many different configuration without specifying more parameters in the yml, e.g.: minimal builds, benchmark builds, march native, clang and in the future asan, tsan, ubsan, valgrind, helgrind...
  • So far, for scheduled builds and workflow dispatch builds, the override parameters specified in the yml were simply ignored.

@dpiparo dpiparo requested a review from guitargeek January 12, 2026 14:06
@dpiparo dpiparo self-assigned this Jan 12, 2026
@dpiparo dpiparo force-pushed the fix_benchmark branch 5 times, most recently from be28e6d to 56a5da2 Compare January 12, 2026 16:18
@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 9397ad8.

♻️ This comment has been updated with latest results.

@dpiparo dpiparo changed the title [ci] Simplify build configuration and pick up specific benchmark options [ci] Simplify build configuration and pick up specific options Jan 12, 2026
@dpiparo dpiparo force-pushed the fix_benchmark branch 13 times, most recently from 81bbfd2 to 7b32260 Compare January 12, 2026 22:38
Builds requiring special configurations can now be defined in the workflow
definition file through the parameter "platform_config". The parsing of such
options has been enhanced. In a nutshell:
1. If "platform_config" is not specified, the platform name is considered instead
and the configuration file <platform>.txt is read. This is for compatibility with
the previous behaviour.
2. If "platform_config" is specified, the file <platform_config>.txt file is read.
3. If the "minimal" option is specified in a platform configuration file, the
global configuration (global.txt) is ignored.
4. If the option CMAKE_GENERATOR is specified in a platform configuration file,
it will be properly passed through the "-G" CMake switch. Previously the value
had to be specified as a workflow parameter and passed as an environment variable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant