capDL-tool+loader-app: C domain schedule init#82
Merged
Conversation
lsf37
commented
Mar 16, 2026
lsf37
force-pushed
the
dyn-domains
branch
2 times, most recently
from
2ee4015 to
9789538
Compare
lsf37
force-pushed
the
dyn-domains-app
branch
2 times, most recently
from
d60aad5 to
850e2f0
Compare
lsf37
commented
Mar 17, 2026
Indanz
approved these changes
Mar 17, 2026
lsf37
force-pushed
the
dyn-domains-app
branch
2 times, most recently
from
dc1c630 to
d65beba
Compare
Add domain schedule initialisation to the capdl-loader-app and corresponding C output to the capDL-tool. Signed-off-by: Gerwin Klein <gerwin.klein@proofcraft.systems>
This was referenced Mar 20, 2026
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
2 participants
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.
Add domain schedule initialisation to the capdl-loader-app and corresponding C output to the capDL-tool.
This PR is on top of #81. I have tested it for current CAmkES applications without domain scheduler, but it turns out we don't have any CAmkES domain scheduler apps in the foundation repositories for testing the actual domain schedule case.
Will look into that separately.