status-react/nix
Jakub Sokołowski d459f6c318
nix: upgrade Gems, Pods, and Gradle dependencies
This is done to help with debugging dependency issues in:
https://github.com/status-im/status-react/pull/13303

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2022-04-27 11:57:19 +04:00
..
deps nix: upgrade Gems, Pods, and Gradle dependencies 2022-04-27 11:57:19 +04:00
lib nix: upgrade nixpkgs, keep Go at 1.14.15 2021-06-15 17:49:33 +02:00
mobile nix: fix call to status-go derivation 2022-03-22 11:01:10 +01:00
pkgs nix: upgrade go-maven-resolver to 1.1.2 2021-10-26 15:39:55 +02:00
scripts ci: upgrade Nix from 2.3.12 to 2.6.1 2022-04-11 12:26:54 +02:00
status-go [#13016] Pass opensea key from env 2022-03-21 13:59:35 +01:00
tools nix: upgrade nixpkgs, keep Go at 1.14.15 2021-06-15 17:49:33 +02:00
DETAILS.md nix: avoid nesting of Nix shells, show errors (#12796) 2021-11-05 12:59:33 +00:00
KNOWN_ISSUES.md ci: upgrade Nix from 2.3.12 to 2.6.1 2022-04-11 12:26:54 +02:00
README.md nix: avoid nesting of Nix shells, show errors (#12796) 2021-11-05 12:59:33 +00:00
config.nix nix: remove obsolete references to Nimbus sources 2021-11-15 13:17:30 +01:00
default.nix Cleanup 2020-01-10 19:59:54 +01:00
nix.conf nix: drop references to nix-cache-cn.status.im 2021-05-25 17:53:47 +02:00
overlay.nix nix: fix gomobile builds requiring Android SDK 2021-11-26 16:22:57 +01:00
pkgs.nix nix: upgrade nixpkgs to current master 2021-11-26 16:22:45 +01:00
shell.nix nix: minor cleanup and documentation updates 2020-06-05 14:49:34 +02:00
shells.nix nix: fix use of androidPkgs in gradle shell 2021-10-26 15:39:54 +02:00
targets.nix drop all desktop related files and references 2020-07-08 10:26:51 +02:00

README.md

Description

This folder contains configuration for Nix, a purely functional package manager used by the Status app for its build process.

Configuration

The main config file is nix/nix.conf and its main purpose is defining the binary caches which allow download of packages to avoid having to compile them yourself locally.

Build arguments

We leverage the config argument of standard nixpkgs for our own parameterization of the builds (e.g. to pass a build number or build type).

Here is a sample structure of the config attribute set:

{
  status-im = {
    build-type = "pr";     # Build type (influences which .env file gets used for feature flags)
    build-number = 9999;   # Used for versionCode and CFBundleVersion in Android and iOS respectively
    android = {
      gradle-opts = "";    # Gradle options passed for Android builds
      keystore-path = "";  # Path to keystore for signing the APK
      abi-split = false;   # If APKs should be split based on architectures
      abi-include = "x86"; # Android architectures to build for
    };
    status-go = {
      src-override = "$HOME/my/source/status-go"; # local source override
    };
  };
}

You can see the defaults in nix/config.nix.

Shell

In order to access an interactive Nix shell a user should run make shell.

The Nix shell is started in this repo via the nix/scripts/shell.sh script, which is a wrapper around the nix-shell command and is intended for use with our main Makefile. This allows for an implicit use of nix-shell as the default shell in the Makefile.

Normally the shell starts without any specific target platform, if you want to change that you should export the TARGET env variable with appropriate value:

make shell TARGET=android

This way your shell and all other nix commands should run in a setup that is tailored towards Android development.

For valid values you can check the nix/shells.nix file.

⚠️ WARNING: To have Nix pick up all changes a new nix-shell needs to be spawned.

Using a local status-go repository

If you need to use a locally checked-out status-go repository, you can achieve that by defining the STATUS_GO_SRC_OVERRIDE environment variable:

export STATUS_GO_SRC_OVERRIDE=$GOPATH/src/github.com/status-im/status-go
make release-android

Resources

You can learn more about Nix by watching these presentations:

And you can read nix/DETAILS.md for more information.

Known Issues

See KNOWN_ISSUES.md.