Skip to content

Conversation

@yaito3014
Copy link
Member

@yaito3014 yaito3014 commented Feb 8, 2026

TODO

  • Add natvis

Post-merge TODO

  • Remove Boost.MPL dependency
  • Remove Boost.Core dependency
  • Limit Boost.PP dependency to development build only
  • Refine X4Attribute to include the default constructible / assignable trait

@yaito3014 yaito3014 added enhancement New feature or request CI Build system issues labels Feb 8, 2026
@yaito3014 yaito3014 self-assigned this Feb 8, 2026
@yaito3014 yaito3014 removed the CI Build system issues label Feb 8, 2026
@saki7
Copy link
Member

saki7 commented Feb 8, 2026

So far so good.

The CI workflow must be changed like below:

  • If "general" files are modified, set a flag to test both alloy and x4
  • If "alloy" files are modified, set a flag to test both alloy and x4
  • If "x4" files are modified, set a flag to test only x4

In other words the "general", "alloy", and "x4" changes must be used for determining whether to build alloy/x4. The last workflow run shows that they're treated like some standalone target, which resulted in building all libraries in duplicated runs.

When the workflow is corrected, it must only show "alloy" and/or "x4" category in the workflow run. No "general" category should be run, because there's no targets placed directly under the test/ directory.

@saki7 saki7 added the CI Build system issues label Feb 8, 2026
@saki7

This comment was marked as resolved.

@saki7

This comment was marked as resolved.

@yaito3014 yaito3014 marked this pull request as ready for review February 10, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Build system issues enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants