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

atom-fstar-build.json needs --verify_module <Module checked> flag. #10

Open
markulf opened this issue Aug 20, 2015 · 2 comments
Open

atom-fstar-build.json needs --verify_module <Module checked> flag. #10

markulf opened this issue Aug 20, 2015 · 2 comments

Comments

@markulf
Copy link

markulf commented Aug 20, 2015

Contrary to what one would expect, the --verify_module flag needs to be manually set in atom-fstar-build.json, to verify individual files.
image

Otherwise, verification is slow, and for miTLS reports way too many errors.

Moreover, if there is in addition a dangling space at the end of the JSON string, the following error is thrown:
image

@fournet
Copy link

fournet commented Aug 20, 2015

Can someone explain or document the json config files, and in particular how the file-local config is merged with the project config? We are getting too many conflict due to check ins of ad hoc atom-fstar-build.json files.

@fournet
Copy link

fournet commented Sep 2, 2015

As mentioned by Markulf, I miss an automated --verify_module on the interactive module; editing the atom-fstar-build.json causes conflicts.

Note also that file-local (*--build-config ... *) entirely override the build file; it is usually a bad idea to mix the two. Instead, use # pragmas.

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