Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tauri dev in local fails to compile #19

Open
pratikIT95 opened this issue Feb 24, 2024 · 0 comments
Open

Tauri dev in local fails to compile #19

pratikIT95 opened this issue Feb 24, 2024 · 0 comments
Labels
investigating Gathering info about the bug

Comments

@pratikIT95
Copy link

While running the tauri dev command, this error related to midir pops up -

>    --> D:\home\.cargo\registry\src\github.com-1ecc6299db9ec823\midir-0.7.0\src\backend\winmm\mod.rs:100:38
>     |
> 100 |         let pname: &[u16] = unsafe { &device_caps.szPname }; // requires unsafe because of packed alignment ...
>     |                                      ^^^^^^^^^^^^^^^^^^^^
>     |
>     = note: `#[allow(unaligned_references)]` on by default
>     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>     = note: for more information, see issue #82523 <https://github.com/rust-lang/rust/issues/82523>
>     = note: fields of packed structs are not properly aligned, and creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)
>     = help: copy the field contents to a local variable, or replace the reference with a raw pointer and use `read_unaligned`/`write_unaligned` (loads and stores via `*p` must be properly aligned even when using raw pointers)
[...]

This seems to be an issue with midir 0.7.0, it needs to be updated to 0.8.0

@pratikIT95 pratikIT95 changed the title Tauri dev in local fails to complete Tauri dev in local fails to compile Feb 24, 2024
@ZaneH ZaneH added the investigating Gathering info about the bug label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Gathering info about the bug
Projects
None yet
Development

No branches or pull requests

2 participants