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

Move gnatprove dependency to nested crate #10

Open
mosteo opened this issue Dec 18, 2023 · 3 comments
Open

Move gnatprove dependency to nested crate #10

mosteo opened this issue Dec 18, 2023 · 3 comments

Comments

@mosteo
Copy link
Member

mosteo commented Dec 18, 2023

To avoid making clients of a SPARK library depend on gnatprove itself, we should move that dependency to a nested prover crate.

@mgrojo
Copy link
Contributor

mgrojo commented Aug 24, 2024

Is there an example at any other place on how to do this in that recommended way?

@mgrojo
Copy link
Contributor

mgrojo commented Aug 24, 2024

By the way, in its current state, the README is inconsistent with the alire.toml and the GitHub action, because it doesn't tell that you have to run alr with gnatprove if you want SPARK proof and the GitHub action working as is.

@mosteo
Copy link
Member Author

mosteo commented Aug 26, 2024

Is there an example at any other place on how to do this in that recommended way?

It is described here: https://alire.ada.dev/docs/catalog-format-spec#using-pins-for-crate-testing , without explicitly mentioning gnatprove (but the idea is the same one).

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

No branches or pull requests

2 participants