The build command failed! Customizable build?

[jpolstre]

The command that generates rinf for building is something like this:

rustup run stable cargo build --manifest-path "...native\hub\Cargo.toml" -p "hub" --target "x86_64-linux-android" --target-dir "...appTest\build\rinf/build"

But this one fails!

I need a customizable build command. In my particular case, this command works:

cargo ndk --bindgen -t x86_64-linux-android -o "...appTest\build\rinf/build" build

Could I add configuration options to initializeRust or something similar?

Maybe something like this:

await initializeRust(
    assignRustSignal,
    config: Config(
      //... other settings
      customBuildCommand: //optional, if not found it follows its normal course
          Platform.isAndroid
              ? (
                BuildEnvironment environment,
                Target target,
                Map<String, String> buildEnvironment,
              ) =>
              //expose runCommand
              runCommand('cargo ndk', [
                '--bindgen',
                '-t',
                target.rust,
                '-o',
                environment.targetTempDir,
                'build',
                 if (!environment.configuration.isDebug) '--release',
              ], environment: buildEnvironment)
              : null,
    ),
  );

Thanks.

[temeddix]

Thank you for leaving the question :)

Rinf uses Cargokit under the hood to automate the build process. To customize the cargo build command, you can create a file native/hub/cargokit.yaml and write some extra arguments or whatever you need in the file.

• https://github.com/irondash/cargokit/blob/main/docs/architecture.md

However, using cargo ndk instead of cargo build can make this problem harder to solve. Is it possible for you to use cargo build and customize it?

[jpolstre]

Thanks, but it doesn't work because I need to replace the command, not just add flags.

[temeddix]

I see. Changing the build process might not be easy, and using cargo ndk manually could be the easiest solution in your particular case. In my opinion, it would be nice to have an option to "disable the automated crate build process of Rinf for Android".

That aside, may I ask you why you need to use cargo ndk? Understanding your use case might help us make better design decisions down the line.