To install the Nix build products without a channel, configure your machine to
use cache.dhall-lang.org, as described in the nix section and then
visit one of the following links:
You can then click the "Help" button in the bottom right corner, which will
show you a nix-env command that you can run to install the prebuilt
executable.
If you have the jq command-line tool installed then you can do this in one
command by running:
You will probably want to use the shared caches hosted at cache.dhall-lang.org
and dhall.cachix.org when doing Nix development. This is not required, but
this will save you a lot of time so that you don't have to build as many
dependencies from scratch the first time.
If your operating system is NixOS then you can add the cache using these NixOS
configuration options to access dhall packages from your declarative configuration file:
Since many tests require HTTP access, you should also add this setting to
your /etc/nix/nix.conf:
sandbox = false
You can build all of the packages by running:
$ nix-build
... or you can run nix-build within each package's respective directory to
build just that one package.
You can install all of the packages by running:
$ nix-env --install --file default.nix
... or you can run the same command within each package's respective directory
to install just that one package.
If you prefer installing the binaries locally in a nix shell environment
instead, just run nix-shell in the top-level directory. This option provides
additional flexibility with respect to overriding some of the default parameters
(e.g. the compiler version), which makes it particularly useful for developers.
You can develop any package by navigating to that package's directory and
running:
If you do need to test changes to the GHCJS code (i.e. the
./dhall-try subdirectory) then stay within this repository, but
edit the dhall/dhall-lang submodule to make the following change:
请发表评论