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 analyze command #14

Closed
vsoch opened this issue Feb 25, 2021 · 2 comments
Closed

Add analyze command #14

vsoch opened this issue Feb 25, 2021 · 2 comments

Comments

@vsoch
Copy link
Member

vsoch commented Feb 25, 2021

  • I think should be considered an extension (or possibly developer type?)
  • the user should be able to select same package options
  • the group (by default) should write to an analyze output folder in package metadata (.spack)
  • optionally, the user can send results to a monitor (and the argument group, since it's the same, should be shared between analyze and install).
  • We should provide analyzers in an analyze/analyzers folder (e.g., abi or even more general, libabigail).
@vsoch
Copy link
Member Author

vsoch commented Feb 25, 2021

More notes for implementation:

  • we can get function for iterating in binary_dependencies
  • write metadata about build in .spack directory (environment)
  • spack analyze should have same arguments as spack install init disambiguate spec
  • write files into .spack/analyze/abi

@vsoch
Copy link
Member Author

vsoch commented Mar 6, 2021

This is all done!

@vsoch vsoch closed this as completed Mar 6, 2021
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

1 participant