5 ms·
It takes about 5 minutes to make a nix expression for a "./configure && make && make install", with most of that time being figuring out the dependencies and ca
by aidenn0 8y ago
It takes about 5 minutes to make a nix expression for a "./configure && make && make install", with most of that time being figuring out the dependencies and calculating the checksum of the tarball.
Example:
https://nixos.org/nix/manual/#ex-hello-nix https://nixos.org/nix/manual/#ex-hello-nix
For any standard build tools (cmake, scons, whatever) it's just one extra line. Applying patches is one extra line. For a non-standard workflow, you can supply a shell script for each step (unpack, configure, build, install, &c.). so it's just however many lines that is.
I've had zero issue getting any source-based third party stuff running. Binaries are a pain, but that's always true if you aren't running the exact distro that the binary was built for.
- Ralith 8y ago> Binaries are a pain, but that's always true if you aren't running the exact distro that the binary was built for. This is actually easier to deal with on NixOS than elsewhere, because the tools for handling that case (patchelf, buildFHSUserEnv, supporting multiple versions of a lib, etc) are so well developed.
- danieldk 8y agoIndeed, just two days ago I made a derivation for a large binary, which is built against an older Boost (1.58). On most other package managers, this would be painful, but with Nix I just made a derivation for that version of Boost by overriding Boost 1.59, which is in nixpkgs: https://github.com/danieldk/nix-home/blob/f6da4d02686224b3008489a743fbd558db689aef/overlays/20-alpino.nix#L4 https://github.com/danieldk/nix-home/blob/f6da4d02686224b300...