Add a clean nix/nixos development enviroment #163
+237
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Check description.
Description
Adds a nix/nixos development with automation though github actions with
Motivation and Context
This change is required because there is currently no default dev enviroment for nix/nixos It solves having an environment to use when developing ferrum there was previously a pr for adding a flake below, but there was a couple problems one it uses flake utils which is a non module based system which means it makes it harder to make things compatible plus is a non nix way of doing, two building the package inside of the devshell is not really required as the user can run
cargo build --release
and then use the bin produced, three it tries to add back the cargo lock file which is only good if your producing a library but ferrumc is producing a binary so it's an unneeded file.Follow up #125.
How has this been tested?
Local using direnv and
nix develop
as well asnix flake check
plus I have also built in a flake check for each pr that is created.Screenshots (if appropriate):
Types of changes
Checklist: