super_native_extensions

To avoid requiring a Rust toolchain on every developer's machine, Cargokit can download and verify precompiled binaries. The workflow follows these steps:

1. Check Configuration: Cargokit looks for cargokit_options.yaml in the target application's root. If use_precompiled_binaries is set to false, it forces a build from source. If the file is missing but rustup is installed, it also builds from source.
2. Verify Crate Support: Cargokit looks for a cargokit.yaml file inside the Rust crate. This file must contain a precompiled_binaries section with a public_key and a url_prefix.
3. Compute Crate Hash: A crate-hash (SHA256) is generated from all Rust files, Cargo.toml, Cargo.lock, and cargokit.yaml. This hash is used to identify the specific version of the binaries needed.
4. Download and Verify: Cargokit attempts to download the binary and its signature for the current platform and crate-hash. It verifies the signature using the public_key from cargokit.yaml.
5. Fallback: If verification fails or download fails, Cargokit falls back to building from source.

To support dragging multiple items simultaneously on iOS, configure the DragItemWidget with canAddItemToExistingSession: true.

In the dragItemProvider callback, you must check if the item is already part of the current session using request.session.hasLocalData(key). If it is already present, return null to prevent the same item from being added multiple times.

  return DragItemWidget(
    allowedOperations: () => [DropOperation.copy],
    canAddItemToExistingSession: true,
    dragItemProvider: (request) async {
      // For multi drag on iOS check if this item is already in the session
      if (await request.session.hasLocalData('image-item')) {
        return null;
      }
      final item = DragItem(
        localData: 'image-item',
        suggestedName: 'Green.png',
      );
      item.add(Formats.png(await createImageData(Colors.green)));
      return item;
    }
  );

You can automate the precompilation and uploading of binaries using a GitHub Action. The action requires two secrets: RELEASE_PRIVATE_KEY (for signing) and RELEASE_GITHUB_TOKEN (for uploading to releases).

Use the dart run build_tool precompile-binaries command to perform the work.

Key Arguments:

• --manifest-dir: Path to the Rust manifest.
• --repository: The repository identifier (e.g., owner/repo).
• --target <rust-triple>: (Optional) Override to build for a specific target.
• --android-sdk-location and --android-ndk-version: Required to build Android binaries.

Example workflow configuration:

on:
  push:
    branches: [ main ]

name: Precompile Binaries

jobs:
  Precompile:
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os:
          - ubuntu-latest
          - macOS-latest
          - windows-latest
    steps:
      - uses: actions/checkout@v2
      - uses: dart-lang/setup-dart@v1
      - name: Install GTK
        if: (matrix.os == 'ubuntu-latest')
        run: sudo apt-get update && sudo apt-get install libgtk-3-dev
      - name: Precompile
        if: (matrix.os == 'macOS-latest') || (matrix.os == 'windows-latest')
        run: dart run build_tool precompile-binaries -v --manifest-dir=../../rust --repository=superlistapp/super_native_extensions
        working-directory: super_native_extensions/cargokit/build_tool
        env:
          GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }}
          PRIVATE_KEY: ${{ secrets.RELEASE_PRIVATE_KEY }}
      - name: Precompile (with Android)
        if: (matrix.os == 'ubuntu-latest')
        run: dart run build_tool precompile-binaries -v --manifest-dir=../../rust --repository=superlistapp/super_native_extensions --android-sdk-location=/usr/local/lib/android/sdk --android-ndk-version=24.0.8215888 --android-min-sdk-version=23
        working-directory: super_native_extensions/cargokit/build_tool
        env:
          GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }}
          PRIVATE_KEY: ${{ secrets.RELEASE_PRIVATE_KEY }}