Skip to content

Migrate to Bazel #46

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

Closed
4 of 8 tasks
tudny opened this issue Mar 24, 2023 · 0 comments
Closed
4 of 8 tasks

Migrate to Bazel #46

tudny opened this issue Mar 24, 2023 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request NITD Not intended to be developed during the JNP3 project.

Comments

@tudny
Copy link
Collaborator

tudny commented Mar 24, 2023

Bazel is becoming more and more popular. We should consider migrating the building procedure from Cargo to Bazel as it allows us to collect all runnables in one place.

Things to do:

  • Define core binary target
  • Define binaries with features
  • Define test targets
  • Define Python Rust target for DFT
  • Remove Cargo.toml
  • Move independent modules into separate crates (e.g., Matrix, Parser etc.)
  • Update CI/CD to Bazel commands
  • Update README/GUIDE if needed to
@tudny tudny added documentation Improvements or additions to documentation enhancement New feature or request NITD Not intended to be developed during the JNP3 project. labels Mar 24, 2023
@tudny tudny self-assigned this Mar 24, 2023
@tudny tudny linked a pull request Mar 24, 2023 that will close this issue
@tudny tudny closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request NITD Not intended to be developed during the JNP3 project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant