Nix Rust | 681 Members | |
| Rust | 155 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Jul 2025 | ||
| And Dioxus uses Tauri for all the OS specific bits | 15:25:50 | |
| So presumably they inherit that limitation | 15:25:58 | |
| 17:00:28 | ||
| 17:17:37 | ||
| I have a single machine. | 17:57:43 | |
| I left this just in case:
| 17:57:57 | |
| Apparently you can bundle the WebView2 Runtime with the app. | 17:58:21 | |
| Moreover, I succeeded and the binary actually produces (unarchives?) the WebView2 directory in the same PWD before the app can be run. | 17:59:27 | |
Download app.jpg | 17:59:51 | |
| Though I need to ask Jon and Evan about this: | 18:00:07 | |
Download 3 things.jpg | 18:00:10 | |
| I assume the CLI binary both, adds the Runtime to PWD and launches the GUI. | 18:00:42 | |
| Really didn't expect a second window to appear when the app launches. | 18:01:18 | |
| It also takes maybe like 30 seconds to copy about 11 MiB of runtime data before the app can actually show up. But after that it launches in one or two seconds. | 18:01:56 | |
| Overall, success. But at what cost... | 18:02:16 | |
| I thought a bit about it, and I think you can't really build any GUI cross-platform/from-Linux app and run it as is on any Windows system. | 18:03:28 | |
| Like for Python you'd have to install Python. Though you can technically bundle everything into a single binary. Not user if it works with GUI apps that use Qt or whatever. | 18:04:22 | |
| Perhaps same problems will arise with C++ apps. | 18:04:56 | |
| So you kinda have to build natively... | 18:05:19 | |
| Although Dioxus Blitz supposedly can be statically linked, since it renders natively. But I haven't looked into this. | 18:06:23 | |
Maybe https://github.com/rust-cross/cargo-xwin can just work. Though no Nix and no native dx support. | 18:55:20 | |
| 7 Jul 2025 | ||
| cargo-llvm-cov added a git dev-dependency in its latest release that isn't reflected in Cargo.lock on crates.io, breaking nixpkgs' "download the lockfile from crates.io and build against that to avoid checking the entire lockfile into nixpkgs" workflow: https://github.com/taiki-e/cargo-llvm-cov/commit/fb528c913f5b5577b6971dae9d99d70babdd42e0 | 06:49:53 | |
| how should i deal with this | 06:49:59 | |
| i can think of two options:
| 06:50:35 | |
| i feel like at this point i would prefer "something else" but i'm not sure what that should/could be | 06:51:42 | |
| since it seems like repeatable builds are really not a priority for this maintainer | 06:51:56 | |
| * cargo-llvm-cov added a git dev-dependency in its latest release that isn't reflected in Cargo.lock on crates.io, breaking nixpkgs' "download the lockfile from crates.io and build against that to avoid checking the entire lockfile into nixpkgs" workflow: https://github.com/taiki-e/cargo-llvm-cov/commit/fb528c913f5b5577b6971dae9d99d70babdd42e0 | 06:52:51 | |
| i guess checking in cargo.lock isn't that uncommon:
| 06:55:59 | |
| * i guess checking in cargo.lock isn't that uncommon:
| 06:56:26 | |
| 07:58:40 | ||