Sender | Message | Time |
---|---|---|
6 Jul 2025 | ||
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 | ||
08:37:31 | ||
There used to be a lot more but I removed most of them... Anyways: In this case I think it is fine to eat the bullet if the lockfile is not crazy large. But in case you really don't want to:
At least I think this could work. | 12:31:15 | |
* There used to be a lot more but I removed most of them... Anyways: In this case I think it is fine to eat the bullet if the lockfile is not crazy large. But in case you really don't want to:
At least I think this could work. | 13:00:29 | |
13:11:39 | ||
yeah i had considered that, but it seems more convoluted and annoying to maintain | 14:26:36 | |
i made a PR that vendors the lockfile last night (about 8 hours ago) and it's merged now, so | 14:27:07 | |
really wish people would just commit their lockfiles | 14:27:49 | |
16:32:49 | ||
18:09:41 | ||
23:28:49 |