1# Mapping non-Haskell dependencies to Nixpkgs
3Cabal files may contain dependencies to external non-Haskell
6* [`build-tool-depends`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-build-tool-depends)
7* [`pkgconfig-depends`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-pkgconfig-depends)
8* [`frameworks`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-frameworks)
9* [`extra-libraries`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-extra-libraries)
11If there is a `pkgs` attribute in Nixpkgs that matches the name given
12in the Cabal file, then it will be added as a dependency (see the
13output of `cabal-to-nix`). Otherwise, there needs to be a mapping from
14Cabal file names (decided by the package author) to Nix package
19The user may solve it by themself by overriding Nixpkgs and adding a
20package alias. For example:
32### Mapping in Haskell.nix
34Alternatively, if the name is commonly used, an alias can be added to
35the Haskell.nix sources, so that it's solved for all users.
37* [`lib/pkgconf-nixpkgs-map.nix`](https://github.com/input-output-hk/haskell.nix/blob/master/lib/pkgconf-nixpkgs-map.nix) - for `pkgconfig-depends`
38* [`lib/system-nixpkgs-map.nix`](https://github.com/input-output-hk/haskell.nix/blob/master/lib/system-nixpkgs-map.nix) - for `build-tool-depends`, `frameworks`, `extra-libraries`, etc.
41 Please go ahead and open a [pull request](https://github.com/input-output-hk/haskell.nix/pulls)
42 to improve the package mappings.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list