Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add landing for GitHub pages, add index to resolved arch #459

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

dhower-qc
Copy link
Collaborator

With this, an index of the architecture files for main will be generated with CI at https://riscv-software-src.github.io/riscv-unified-db/resolved_arch/index.yaml (and the paths in the index are relative to https://riscv-software-src.github.io/riscv-unified-db/resolved_arch).

@dhower-qc dhower-qc requested review from drom and AFOliveira February 11, 2025 16:06
@dhower-qc
Copy link
Collaborator Author

closes #458

@dhower-qc
Copy link
Collaborator Author

closes #199

Copy link
Collaborator

@AFOliveira AFOliveira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@drom
Copy link
Collaborator

drom commented Feb 12, 2025

I need just index.json "non resolved" version of index.
The index should allow fetching of ALL required parts and iterative resolution at later time.

@dhower-qc
Copy link
Collaborator Author

In this case, the "non resolved" and "resolved" indices are the same. Resolution of the standard doesn't add or remove any files, and since the index holds relative paths you could use it to search arch/ as well.

Keep in mind that "resolved" means (a) merged with overlay (a no-op for the RVI standard) and (b) $inherits expansion. It does not expand $ref, so I think for your use cases you could use the "resolved" files generated at deployment.

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.

3 participants