Skip to content

Memory migration v2#246

Draft
KrishaDeshkool wants to merge 5 commits intoeclipse-score:mainfrom
KrishaDeshkool:memory-migration-v2
Draft

Memory migration v2#246
KrishaDeshkool wants to merge 5 commits intoeclipse-score:mainfrom
KrishaDeshkool:memory-migration-v2

Conversation

@KrishaDeshkool
Copy link
Contributor

No description provided.

@KrishaDeshkool KrishaDeshkool force-pushed the memory-migration-v2 branch 5 times, most recently from 843b199 to 6f7f39d Compare March 26, 2026 16:08
Add boost.container to MODULE.bazel deps required by the local score/memory
library. Configure .bazelrc to use the local baselibs checkout as an override
so the in-tree score/memory sources are resolved instead of the registry copy.
Add the score/memory shared-memory library sources, headers, tests, and design
documentation copied from the baselibs repository. This brings the library
in-tree so communication can depend on it directly without an external
Bazel module reference.
Define cc_library, cc_test, and related Bazel targets for the score/memory
shared-memory library that was copied in-tree. All targets use the repo-local
label //score/memory/... rather than the external @score_baselibs//score/memory/...
Replace all @score_baselibs//score/memory/... dependency labels in
score/mw/com BUILD files with the in-tree //score/memory/... equivalents
now that the library has been copied locally.
Update #include paths and namespace references in score/mw/com sources to
reflect that AtomicIndirector and related types are now accessed via
concurrency::atomic:: rather than memory::shared:: following the in-tree
copy of the score/memory library.
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