status-react/nix
Jakub Sokołowski c4b13eb043
nix: use builtins to not depend on channels
We use `builtins.fetchTarball` to avoid having to first import a
`nixpkgs` from existing channels, which breaks if there are no channels.

Otherwise new Nix 2.14 version can result in:
```
error: file 'nixpkgs' was not found in the Nix search path (add it using $NIX_PATH or -I)
```
Which happens due to no default `nixpkgs` channel existing:
```
 > nix-channel --list

```
Resolves: https://github.com/status-im/status-mobile/issues/16342

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-06-21 15:36:08 +02:00
..
deps Upgrade `react-native-camera-kit` library to resolve camera issues in Sign In screen (#16248) 2023-06-20 18:50:05 +05:30
lib
mobile upgrade `react-native` from 0.67.5 to 0.69.10 (#16016) 2023-06-14 07:17:41 +05:30
pkgs nix: upgrade nixpkgs to latest nixos-22.11 2023-06-20 12:53:06 +02:00
scripts nix: add upgrade script for Nix interpreter 2023-06-19 12:21:00 +02:00
status-go Upgrade `react-native` from 0.63.3 to 0.67.5 (#15486) 2023-04-12 15:25:19 +05:30
tools
DETAILS.md nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
KNOWN_ISSUES.md nix: fix applying nix.conf by using correct env var 2023-06-20 13:55:07 +02:00
README.md
config.nix
default.nix
nix.conf nix: fix applying nix.conf by using correct env var 2023-06-20 13:55:07 +02:00
overlay.nix nix: upgrade nixpkgs to latest nixos-22.11 2023-06-20 12:53:06 +02:00
pkgs.nix nix: use builtins to not depend on channels 2023-06-21 15:36:08 +02:00
shell.nix nix: upgrade nixpkgs to latest nixos-22.11 2023-06-20 12:53:06 +02:00
shells.nix nix: upgrade nixpkgs to latest nixos-22.11 2023-06-20 12:53:06 +02:00
targets.nix

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
      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.