cry/nixide
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Oxidized bindings for the Nix package manager!!
132 commits 1 branch 0 tags 903 KiB
Find a file
Robert Hensing 32136109fc maint: Ask GCC for system headers 
In the previous update commit, the Nix `cc.version` didn't match the
in-output directory name anymore, causing a build failure.

By asking GCC properly, we are robust against such discrepancies.

The script isn't great, relying on GCC "log" output specifics, but it
seems that the GCC output has been like this for a while, and the
lines before and after seem to be intentional about their purpose...

(cherry picked from commit 68f928555660cb914105b0ad668d6cadc25223e9)
2025-10-04 02:31:16 +02:00
.claude refact: Move dev-only dependencies into separate lock file 2025-10-04 02:31:16 +02:00
.vscode dev: Add indentation rules to .vscode 2025-09-30 19:02:44 +02:00
dev maint: Ask GCC for system headers 2025-10-04 02:31:16 +02:00
doc/hacking feat: Add manual testing of bindings with Valgrind 2025-09-30 18:45:54 +02:00
rust maint: Ask GCC for system headers 2025-10-04 02:31:16 +02:00
.envrc feat: Rust skeleton 2025-09-30 17:57:50 +02:00
.gitignore feat: Rust skeleton 2025-09-30 17:57:50 +02:00
flake.lock flake.lock: Update 2025-10-04 02:31:16 +02:00
flake.nix maint: Update Nix 2025-10-04 02:31:16 +02:00
README.md feat: Rust skeleton 2025-09-30 17:57:50 +02:00

README.md

nix_bindings_* crates

Use the Nix C API from Rust.

Hacking

The following will open a shell with dependencies, and install pre-commit for automatic formatting.

$ nix develop

VSCode

rust-analyzer

If the rust-analyzer extension fails, make sure the devShell was loaded into VSCode via Nix Env Selector or direnv.