fix: maturin develop can compile on macOS with M1/M2 chip

[dzvon]

#1013

This fix can make maturin develop compile successfully in my local environment.

[netlify]

✅ Deploy Preview for maturin-guide canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f3a5827
🔍 Latest deploy log	https://app.netlify.com/sites/maturin-guide/deploys/62d65ddccca6200008852646

[messense]

L38 and L40 change is wrong. We want to respect Python architecture to fix #982 and #979. target is default Rust target we get from rustc -vV.

[messense]

Based on the discussion in #1013, can you add a debug print here and paste the output here.

println!("{} {:?}", platform, target.target_arch());

[dzvon]

macosx-10.14.6-arm64 Aarch64

@messense

[messense]

Then the offending code shouldn't be these two I think? It might be related to the target_triple variable, can you try #1016 ?

[dzvon]

But if I append --target aarch64-apple-darwin, it works fine.

[messense]

Then you have to debug further, based on the macosx-10.14.6-arm64 Aarch64 output it shouldn't reach these two lines.

[messense]

Try add println!("{:#?}", build_options); just above

maturin/src/develop.rs

Line 68 in 86b5dfc

let build_context = build_options.into_build_context(release, strip, true)?;

[dzvon]

BuildOptions {
    platform_tag: [
        Linux,
    ],
    interpreter: [
        "/Users/pvon/Documents/string_sum/.env/bin/python",
    ],
    find_interpreter: false,
    bindings: None,
    out: Some(
        "/var/folders/0r/tkx69nhn6vg6sr0w1c6nnsxr0000gn/T/.tmpAolWXa",
    ),
    skip_auditwheel: false,
    zig: false,
    universal2: false,
    cargo: CargoOptions {
        quiet: false,
        jobs: None,
        profile: None,
        features: [],
        all_features: false,
        no_default_features: false,
        target: None,
        target_dir: None,
        manifest_path: None,
        ignore_rust_version: false,
        verbose: 0,
        color: None,
        frozen: false,
        locked: false,
        offline: false,
        config: [],
        unstable_flags: [],
        timings: None,
        future_incompat_report: false,
        args: [],
    },
}

[messense]

Nothing seems wrong, I can't reproduce this issue, so you have to debug on your own.

Try to track down where did the target triple changed to x86_64.