our change from string -> str to evade the warnings nix generates, resulted in a bunch of
unforseen consequences.
We now modify the str type a bit for our own use.
* tests: Add test case with fully static build of pandoc
It uses the musl libc. To try it, use:
nix-build test/default.nix \
--arg crossSystem '(import <nixpkgs/lib>).systems.examples.musl64' \
-A fully-static.pandoc-gmp
This includes the GMP library (linked statically). To build one without GMP:
nix-build test/default.nix \
--arg crossSystem '(import <nixpkgs/lib>).systems.examples.musl64' \
-A fully-static.pandoc-integer-simple
Unfortunately, the latter doesn't work (it says "ghc" command not found).
* fixup! tests: Add test case with fully static build of pandoc
Project flags (from stack.yaml and plan.json) are exported in a modules attribute by stack-to-nix and plan-to-nix, but are not currently used. This change updates `mkStackPkgSet` and `mkCabalProjectPkgSet` so that the modules attribute is used (if present) and includes tests to check they are.
This commit makes `stdenv.lib.mkOverride` necessary for setting flags in `mkCabalProjectPkgSet` modules, however it also means that you can set them in `cabal.project` instead (see #254).
Uses the `isLocal` for property set by `plan-to-nix` and `stack-to-nix`
on packages where the source is referenced in the `cabal.project`
or `stack.yaml` file.
* Filter components using buildable flag
* Bump nix-tools
* Include components without buildable flag
* Test buildable components are filtered correctly
* Fix issue with testWrapper (exposed by #238)
We were relying on the `string` type's merge function quietly
concatenating strings.
Described here:
700cc56a0e/lib/types.nix (L218-L221)
