1# Mapping non-Haskell dependencies to Nixpkgs
3Cabal files may contain dependencies to external non-Haskell
5* [`build-tool-depends`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-build-tool-depends)
6* [`pkgconfig-depends`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-pkgconfig-depends).
7* [`frameworks`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-frameworks)
8* [`extra-libraries`](https://cabal.readthedocs.io/en/latest/developing-packages.html#pkg-field-extra-libraries)
10If there is a `pkgs` attribute in Nixpkgs that matches the name given
11in the Cabal file, then it will be added as a dependency (see the
12output of `cabal-to-nix`). Otherwise, there needs to be a mapping from
13Cabal file names (decided by the package author) to Nix package
18The user may solve it by themself by overriding Nixpkgs and adding a
19package alias. For example:
31### Mapping in Haskell.nix
33Alternatively, if the name is commonly used, an alias can be added to
34the Haskell.nix sources, so that it's solved for all users.
36* [`lib/pkgconf-nixpkgs-map.nix`](https://github.com/input-output-hk/haskell.nix/blob/master/lib/pkgconf-nixpkgs-map.nix) - for `pkgconfig-depends`
37* [`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.
40 Please go ahead and open a [pull request](https://github.com/input-output-hk/haskell.nix/pulls)
41 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