rvolosatovs / nixify Goto Github PK

Documentation is outdated, many things mentioned are not actually required

This is a tracking issue for addressing rust-lang/cc-rs#948 in the zig-cc script

Currently compilation of Rust projects linking to C libraries is broken or at least flaky.
It's not a priority for me personally, but it would be nice to have.

It appears that nix flake check is being killed due to OOM

This is a continuation from this issue

I have a repo here:

https://github.com/mamcx/RustStoreNix/tree/nixify

I must compile on macOS, Linux with targets windows, linux musl, android, ios. But my major problem is with android. I need:

def archTriplets = [
        'armeabi-v7a': 'armv7-linux-androideabi',
        'arm64-v8a'  : 'aarch64-linux-android',
]

I tried with:

❯ nix --version
nix (Nix) 2.18.1

{
  inputs.nixify.url = github:rvolosatovs/nixify;

  outputs = {nixify, ...}:
    nixify.lib.rust.mkFlake {
      src = ./.;
      name = "rust-workspace";

      build.workspace = true;
      clippy.workspace = true;
      test.workspace = true;
    };
}

And get :

❯ nix develop
warning: Git tree '/Users/mamcx/Proyectos/Apps' is dirty
(nix:nix-shell-env) bash-5.2$ cargo build
+ command cargo build
   Compiling ring v0.17.6
   Compiling zstd-sys v2.0.9+zstd.1.5.5
   Compiling generic-array v0.14.7
   Compiling globset v0.4.14
   Compiling rustix v0.38.26
   Compiling pin-project v1.1.3
   Compiling walkdir v2.4.0
   Compiling libsqlite3-sys v0.27.0
   Compiling tracing-subscriber v0.3.18
   Compiling thiserror v1.0.50
   Compiling phf_codegen v0.11.2
   Compiling phf v0.11.2
   Compiling parse-zoneinfo v0.3.0
error: linking with `cc` failed: exit status: 1

It most probably has to do with libiconv linking

Note that there's no native support for wasm32-unknown-unknown in nixpkgs, so the target should be treated as just WASI

Is there an existing issue for this?

• I have searched the existing issues

Description

Rather than generating target-specific outputs based upon targets in rust-toolchain.toml, use a custom toolchain per-target and provide builds for various targets out-of-the-box

Acceptance Criteria

No response

Suggestions for a technical implementation

merge the rust-toolchain.toml toolchain with additional target per-output

fmt and clippy checks are added even when these components are not in the rust-toolchain.toml, that should be fixed

Both components and profile should be checked