[Important] Adds advanced flake.nix for $ nix build github:KhronosGroup/OpenCL-ICD-Loader and more #261
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.
Hi there,
Currently I'm working on standardizing, further specifying and simplifying the build, test and release of all the GPU based software for nix: which should eventually allow all standard bodies and hardware/software vendors to further standardize their build workflows.
We already have
khronos-ocl-icd-loaderon nixpkgs here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/kh/khronos-ocl-icd-loader/package.nixThis
flake.nixserves as an additional release channel for a direct specific github branch on any machine that hasnixvia:Also serves as a further documentation as code for all the important build targets.
It also standardizes the builds under a single command:
A contributor can have standardized development environment via:
Lastly, in the future, if there is enough interest, this could enhance the existing CI workflow(with additional PRs) via:
$ nix flake check --all-systems # Runs all the checks(unit tests, pkg-config checks etc) on all CPU architecturesOn a corollary note, I suggest all software developers to install and use nix for all its benefits. I think there is enough documentation online, however I currently find the documentation lacking for conventions around testing. So I documented it here for the ones interested: https://gist.github.com/izelnakri/06d7286fe9ab5f15acee9cbeace1c1b1