Cannot compile on MacOS (M2 MB Air)

[amycol]

I cannot get Pineflash to compile on MacOS, M2 Macbook Air. Following the manual build instructions I get this after cargo build --release:

amy@Mac PineFlash % cargo build --release
   Compiling pineflash v0.5.5 (/Users/amy/Documents/Projects/Pinecil/PineFlash)
error: 1 positional argument in format string, but no arguments were given
   --> src/main.rs:532:88
    |
532 |         Err(error) => panic!("A massive error occured, not sure whats goin on here: \n {}"),
    |                                                                                        ^^

warning: unused imports: `ImageSource` and `epaint::ColorImage`
  --> src/main.rs:12:27
   |
12 | use eframe::{egui::{self, ImageSource}, epaint::ColorImage};
   |                           ^^^^^^^^^^^   ^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

warning: unused variable: `error`
   --> src/main.rs:532:13
    |
532 |         Err(error) => panic!("A massive error occured, not sure whats goin on here: \n {}"),
    |             ^^^^^ help: if this is intentional, prefix it with an underscore: `_error`
    |
    = note: `#[warn(unused_variables)]` on by default

warning: `pineflash` (bin "pineflash") generated 2 warnings
error: could not compile `pineflash` (bin "pineflash") due to 1 previous error; 2 warnings emitted

[amycol]

Just tried the generic_unix_install.sh script and had the same error. I was expecting this but thought to try it anyway to rule out the possibility that I typed a command wrong or something.

[acuteaangle]

Duplicate of gh-87

After cloning the repo, you could trying running either git checkout a823625 to revert the problematic commit, or git checkout 0.5.5 to get the latest release version.

[lepaapel]

Not sure that correct but helps me - just remove {} at src/main.rs:532

[acuteaangle]

That works. The ‘better’ solution would be to replace the missing argument, as in gh-86.

[acuteaangle]

This should now be resolved by gh-86.

[Spagett1]

Should be resolved by the recent PR #86 , if the issue persists please feel free to reopen.